From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] transferring contents of /etc/conf.d to the config files
Date: Mon, 10 Oct 2011 19:50:18 +0200 [thread overview]
Message-ID: <20111010195018.47488ae7@rohan.example.com> (raw)
In-Reply-To: <20111010173352.GA2844@solfire>
On Mon, 10 Oct 2011 19:33:52 +0200
meino.cramer@gmx.de wrote:
> Hi,
>
> I have read several docs to figure out this...all docs do changes
> in /etc/conf.d but I found no hint how to transfer that settings
> to the "real" configuration files of the according programs.
>
> env-update & etc-update do not help...
>
> What tool do I have to call to acchieve this?
>
> Thank you very much in advance for any help!
That's not how it works.
The files in /etc/conf.d are not "included" in config files at all,
they are arguments used when the app is launched.
For example, sshd:
SSHD_CONFDIR="/etc/ssh"
SSHD_OPTS=""
SSHD_PIDFILE="/var/run/sshd.pid"
SSHD_BINARY="/usr/sbin/sshd"
None of those items can go in sshd_config except maybe the pid file,
but that can be specified on the command-line.
The Gentoo init system reads conf.d and uses the info in it to
determine hwo to launch the app.
There is other stuff in /etc/conf.d not related to specific daemons,
but the same principle applies - the system reads the files and does
the appropriate thing at strat-up.
I believe you may have the intent of conf.d and env.d confused?
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2011-10-10 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 17:33 [gentoo-user] transferring contents of /etc/conf.d to the config files meino.cramer
2011-10-10 17:47 ` [gentoo-user] " Nikos Chantziaras
2011-10-10 18:45 ` meino.cramer
2011-10-10 18:53 ` Nikos Chantziaras
2011-10-10 19:13 ` meino.cramer
2011-10-10 19:28 ` Canek Peláez Valdés
2011-10-10 21:49 ` Nikos Chantziaras
2011-10-10 17:50 ` Alan McKinnon [this message]
2011-10-10 17:56 ` [gentoo-user] " Canek Peláez Valdés
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111010195018.47488ae7@rohan.example.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox