-------- Original Message -------- Subject: Re: [Box-Admins] How does Jenkins start? From: Frank Shearar frank.shearar@gmail.com Date: Sun, February 09, 2014 3:14 pm To: Ken Causey ken@kencausey.com
...
What causes you to doubt the use of /etc/default/jenkins to set the variable? If you look at /etc/init.d/jenkins there is a line there that sources (loads) /etc/default/jenkins prior to the use of the variable. But I see that it is now set at the bottom so likely you decided to try this and I'm a bit late.
I haven't edited any files yet.
In FreeBSD at least, /etc/default/* isn't for editing; the foo service script will read in the /etc/default/foo but then also read in another script (in FreeBSD that's /etc/rc.config, IIRC) that overrides the defaults.
It's been quite a few months since I last worked on an init.d service, and expected a similar setup: some kind of source of overrides.
frank
Ken
I agree with you that it seems there should be another level, for local configuration, in a separate location but I don't believe that has become standard policy in Debian. Of course many programs will have their own separate configuration files and I have to wonder if what you want to change can't be changed in a jenkins specific config file. But I double checked and /etc/default/jenkins is marked in the package as a configuration file meaning that upgrading the package won't simply stomp the file before asking.
Ken