Re: [gentoo-user] saslauthd startup parameters
Adam Carter adamcart...@gmail.com writes: where are we supposed to set the parameters for saslauthd? I edited /etc/init.d/saslauthd, and that's probably not the right place to put them? There's probably a saslauthd file in /etc/conf.d Hm, I need to check again to be sure whether there is or isn't. If there is, then how is it included into the startup script? And why isn't there anything in /etc/default for it, where I would expect it? Or, more general, what are the criteria with Gentoo whether to put such a file into /etc/default or into /etc/conf.d? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] saslauthd startup parameters
On Mon, 23 Feb 2015 01:07:55 +0100, lee wrote: There's probably a saslauthd file in /etc/conf.d Hm, I need to check again to be sure whether there is or isn't. If there is, then how is it included into the startup script? And why isn't there anything in /etc/default for it, where I would expect it? Or, more general, what are the criteria with Gentoo whether to put such a file into /etc/default or into /etc/conf.d? /etc/conf.d is an openrc feature. Any script in /etc/init.d should read the corresponding file in conf.d. It is openrc's way of separating configuration from the init scripts. If the file doesn't exist, create it, but most packages include an example conf.d file. -- Neil Bothwick Did you hear about the blind prostitute? You have to hand it to her. pgpoN55CRN0ek.pgp Description: OpenPGP digital signature
Re: [gentoo-user] saslauthd startup parameters
where are we supposed to set the parameters for saslauthd? I edited /etc/init.d/saslauthd, and that's probably not the right place to put them? There's probably a saslauthd file in /etc/conf.d
