On Thu, 1 Nov 2012 18:21:14 -0700 Don Armstrong <d...@donarmstrong.com> wrote:
> Control: severity -1 minor > Control: tag -1 wontfix > > On Tue, 30 Oct 2012, Cedric Jeanneret wrote: > > unscd package should provide an executable named unscd, and its > > configuration file should be "/etc/unscd.conf". > > Currently, the unscd package provides > > "unscd" init-file > > "nscd" executable > > "nscd.conf" configuration file > > unscd is a drop in replacement for nscd, so it uses the exact same > configuration file and the exact same executable. > > It's possible to provide a /usr/sbin/unscd and a /usr/sbin/nscd > symlink, but it's not particularly necessary. well, it's just in order to get a consistent package naming… Having "unscd" package with "unscd" init-script, I'm tempted to say "the executable is unscd - oh crap! it isn't!" > > > This comment is obviously false: > > - file doesn't exist, it's /usr/share/doc/unscd/NEWS.Debian.gz > > - the package "nscd" tells us to install unscd in order to have > > stable host caching > > That again is in order to have unscd be a drop in replacement. > Otherwise, the user will be prompted to replace the default nscd > configuration file. err, if this allow the user to activate the host caching [by default], this may be good, doesn't it? As nscd tells us "hey install unscd, it's better and you can have host caching", I was a bit surprised to see the option deactivated by default… More over, having a wrong documentation link in a config file is just bad. This very point should be corrected I think, don't you? Cheers, C. > > > Don Armstrong > -- Cédric Jeanneret | System Administrator 021 619 10 32 | Camptocamp SA cedric.jeanne...@camptocamp.com | PSE-A / EPFL www.camptocamp.com | www.github.com/camptocamp
signature.asc
Description: PGP signature
