From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: transferring contents of /etc/conf.d to the config files
Date: Tue, 11 Oct 2011 00:49:31 +0300 [thread overview]
Message-ID: <j6vp9c$pnj$1@dough.gmane.org> (raw)
In-Reply-To: <20111010191322.GA4152@solfire>
On 10/10/2011 10:13 PM, meino.cramer@gmx.de wrote:
> Nikos Chantziaras<realnc@arcor.de> [11-10-10 20:56]:
>> On 10/10/2011 09:45 PM, meino.cramer@gmx.de wrote:
>>> Nikos Chantziaras<realnc@arcor.de> [11-10-10 19:52]:
>>>> On 10/10/2011 08:33 PM, meino.cramer@gmx.de wrote:
>>>>> 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.
>>>>
>>>> These *are* real configuration files and you don't need to transfer
>>>> anything.
>>>
>>> The reason I thought, that those settings in /etc/conf.d is due
>>> to a warning of the rkhunter tool:
>>> [...]
>>> Now I see, that it seems to check simply the wrong file.
>>
>> It's checking the correct file. Simply edit /etc/ssh/sshd_config to
>> your liking. /etc/conf.d/ is not for those kind of settings; it's
>> read-in by Gentoo's init system and other infrastructure.
>
> Now I am a little more confused...
>
> What is the purpose of this file? :
>
> /etc/conf.d/sshd
It's used by Gentoo's init system, not by ssh.
> if /etc/ssh/sshd_config is for configuration of sshd's options...for
> what purpose is /etc/conf.d/sshd then ?
>
> And what files gets overwritten when installing a new version of sshd?
All files are overwritten. In case of differences, emerge will tell you
about it at the end of the emerge (even if you emerged multiple
packages, the notification will only appear at the end of all of them.)
Configuration protection is a basic feature of portage. When emerge
tells you that the newly installed configuration files differ from the
existing ones, it means that you need to run 'dispatch-conf' (or another
equivalent tool) that will show you what those differences are and will
allow you to merge them. Until you do that, the new config files will
keep their temporary names ("._cfg" prefix).
next prev parent reply other threads:[~2011-10-10 21:51 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 [this message]
2011-10-10 17:50 ` [gentoo-user] " Alan McKinnon
2011-10-10 17:56 ` 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='j6vp9c$pnj$1@dough.gmane.org' \
--to=realnc@arcor.de \
--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