[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#275403: preinst NSS restart does not work with file-rc



Hi,

At Fri, 8 Oct 2004 10:04:16 +0200,
Christian Hammers wrote:
> On 2004-10-08 GOTO Masanori wrote:
> > >   for service in $services; do
> > >     idl=$(ls /etc/rc${rl}.d/S??${service} 2> /dev/null | head -1)
> > >     echo -n "  $service: stopping..."
> > >   ...
> > > 
> > > This does not work when file-rc is installed which uses
> > > /etc/runlevel.conf to manage the script to runlevel mapping.
> > > 
> > > If you can, use invoke-rc.d
> > 
> > Please look at the above line to check filerc issue:
> > 
> >       if [ -f /usr/share/file-rc/rc -o -f /usr/lib/file-rc/rc ] && [ -f /etc/runlevel.conf ];
> >           idl=$(filerc $rl $service)
> >       else
> >           idl=$(ls /etc/rc${rl}.d/S??${service} 2> /dev/null | head -1)
> >       fi
> > 
> > If this kind of code is sufficient for you, I put this modification.
> 
> - I have none of  /usr/share/file-rc/rc /usr/lib/file-rc/rc, just 
>   /etc/runlevel.conf so make it at least an "-o" and not "&&".

When woody's file-rc is installed, /usr/share/file-rc/rc and
/usr/lib/file-rc/rc are existed.  The above code in libc6.postinst is
used when you upgrade from woody to sarge, so "file-rc" should be
woody's version.

> - At least in the current Debian Sarge filerc package is no binary called
>   'filerc' so the idl=$(...) line is wrong.

No, again, look at the postinst.  filerc is defined in libc6.postinst.

> As I don't know if there are backward compatibility issues you should better
> contact the file-rc maintainer to get recommends how to search and start/stop
> entries from runlevel.conf.

You reported "(libc6.) preinst NSS restart does not work with
file-rc".  However file-rc is used in _postinst_ because restart is
done in postinst.

Moreover, this restart code is used only when you upgrade from woody
to sarge.  I think you misunderstand why this code is existed.  Did
you get any problems with this issue?  If you really had trouble with
it, please report with more information (ex: upgrade messages and so
on).  If not, please let me know; I'll close this bug.

Regards,
-- gotom



Reply to: