Re: Configuration flexibility regarding file paths
Roy Marples
Thu Apr 29 18:06:00 2010On Thu, 2010-04-29 at 13:35 +0300, Ciprian Dorin, Craciun wrote: > > You can tailor the paths at compile time. > > Agree, but this doesn't allow the administrator to "customize" the > run-time without re-compiling the package by hand. One of the reasons why I want to enforce this is because it makes it harder for external entities to find things. Imagine this in dhcpcd.conf pidfile /foo.pid leasefile /lease.foo controlfile /ctrl.com And starting dhcpcd dhcpcd --configfile /abc Taking all that into account, how is dhcpcd-dbus supposed to talk to dhcpcd? By this I'm talking about out of the box config. I have also written several scripts that try to extract this information from ntp, wpa_supplicant, dhclient and many other programs and it's not pretty and is prone to breakage. > > I don't want to support any runtime path changes. > > Fair enough. I'll stop here with this proposal. Good. I only feel it's fair to explain why also :) Thanks Roy
Attachment:
signature.asc
Description: This is a digitally signed message part
| Configuration flexibility regarding file paths | Ciprian Dorin, Craciun |
| Re: Configuration flexibility regarding file paths | Roy Marples |
| Re: Configuration flexibility regarding file paths | Ciprian Dorin, Craciun |