This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Installing configuration files - Was: Add systemd unit file for nscd
- From: Allan McRae <allan at archlinux dot org>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-alpha at sourceware dot org, Andreas Jaeger <aj at suse dot com>, Carlos O'Donell <carlos at systemhalted dot org>
- Date: Sat, 11 May 2013 16:14:24 +1000
- Subject: Installing configuration files - Was: Add systemd unit file for nscd
- References: <1367302602-21639-1-git-send-email-allan at archlinux dot org> <201305101142 dot 11739 dot vapier at gentoo dot org> <518D8959 dot 8020907 at archlinux dot org> <201305110044 dot 41617 dot vapier at gentoo dot org>
On 11/05/13 14:44, Mike Frysinger wrote:
> On Friday 10 May 2013 19:57:13 Allan McRae wrote:
>> On 11/05/13 01:42, Mike Frysinger wrote:
>>> On Friday 10 May 2013 02:22:59 Andreas Jaeger wrote:
>>>> A future followup patch could install these files - and then we should
>>>> change the path as well.
>>>
>>> that suggestion (and patch) was posted previously and decided to not do
>>> it
>>
>> Can you point me to that discussion? I have searched and am unable to
>> find this.
>
> http://sourceware.org/ml/libc-alpha/2011-09/msg00098.html
What I get from that thread, all distribution maintainers we in favour
of installing nscd.conf and gai.conf (not nsswitch.conf) by default.
And they are already distributed in the packages supplied by most
distributions. So installing them reduces the packaging overhead for
most distro maintainers as it saves them manually installing these files.
The reject email [1] has two points:
#1) nscd.conf needs customised. Not really a good point as it appears
most distros ship it as is or do a minor sed on it. Also not installing
it means an individual has to figure out the defaults or create the
entire file from scratch.
#2) installing gai.conf slows everything down. The default file is all
comments, so on the first read it is just skipping all lines - so a slow
down there. From then on it is cached and not read unless it changes.
Also, most distros ship this, so the slowdown is already present.
I think that patch would be fine to be pushed under the community
agreement model we use in glibc now and should be revisited...
[1] http://sourceware.org/ml/libc-alpha/2011-10/msg00002.html
Allan