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

Bug#623377: init: don't start in runlevel S *and* 2345



On Tue, 2011-04-19 at 20:40 +0200, Michael Biebl wrote:
> Package: nfs-common, portmap, rpcbind
> Severity: important
> 
> 
> Hi,
> 
> the initscripts of nfs-common, pormap and rpcbind all have the following in
> their LSB header:
> 
> # Default-Start:     S 2 3 4 5
> # Default-Stop:      0 1 6
> 
> 
> As a result, the init scripts are run *twice* when you boot your system.
> More importantly though, this breaks systemd horribly, as this leads to a
> depedency loop there.

Then perhaps the conversion of runlevels into dependencies is wrong?

> nfs-common, portmap and rpcbind are the only packages using such a strange setup
> in Default-Start.
> 
> I can't really tell, if those packages are supposed to be started during early
> boot (rcS) and be running in single-user mode or starting them in multi-user is
> sufficient.
[...]

All filesystems listed in /etc/fstab should be mounted even in single-
user mode.  If any of those are mounted over NFS, rpc.statd and portmap
or rpcbind must be started.

Additional daemons may be required for multi-user access; those are
installed in /usr.  And so it may be necessary to run nfs-common a
second time, when those daemons are available.

*However*, all of these daemons (except the obsolete portmap) are now
linked to libtirpc, which is currently installed in /usr.  So this
doesn't work right now.

I suppose we should split the init script, assuming that people stuck in
the 90s continue to insist that separate /usr must be supported.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: