Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-17 Thread Petter Reinholdtsen
[Andy Chittenden] > I think using LDAP as a Network Information Service (see RFC2307) > may be relevant here. I don't know whether that's possible on Linux > at the moment but I would guess that if it is (or ever will be) then > it may not involve ypbind. So perhaps that's pointing towards > /etc/i

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-17 Thread Andy Chittenden
> Or should nis say it provides nis as well as what it currently says > it provides or instead of? I think using LDAP as a Network Information Service (see RFC2307) may be relevant here. I don't know whether that's possible on Linux at the moment but I would guess that if it is (or ever will be)

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-14 Thread Petter Reinholdtsen
[Andy Chittenden] > having had a look at /etc/init.d/nis, I see it says: > > # Provides: ypbind ypserv ypxfrd yppasswdd > > So, I thought perhaps autofs shouldn't say nis in Should-Start but > should say ypbind. Having done that and rerun insserv, the start > files look ok: Good. Th

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-14 Thread Andy Chittenden
having had a look at /etc/init.d/nis, I see it says: # Provides: ypbind ypserv ypxfrd yppasswdd So, I thought perhaps autofs shouldn't say nis in Should-Start but should say ypbind. Having done that and rerun insserv, the start files look ok: ws-andyc-debian64:~# ls /etc/rc*d/*{nis,

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-14 Thread Petter Reinholdtsen
[Andy Chittenden] > Once I'd done that, autofs is still starting before nis: I had a closer look at the nis script, and it do not provide nis (which I expected it to do), but ypbind, ypserv, ypxfrd and yppasswdd. The init.d dependency relations are to the strings provided by other scripts, so this

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-14 Thread Andy Chittenden
Having applied your patch to autofs and reenabling insserv, I had to reinstall portmap to get its links in /etc/rc*d so that when nis started, the portmapper was enabled. Once I'd done that, autofs is still starting before nis: ws-andyc-debian64:~# ls /etc/rc*d/*{nis,autofs} /etc/rc0.d/K01autof

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-13 Thread Petter Reinholdtsen
[Petter Reinholdtsen] > I'll have a look at binfmt-support, edac, fancontrol, mercury-base, > nvidia-glx, nvidia-kernel, snmpd, sysklogd, syslog-ng, uml-utilities > and winbind to see if these are buggy too. I suspect most of these > are just fine starting without a running syslog collector. For

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-13 Thread Petter Reinholdtsen
reassign 541349 autofs retitle 541349 autofs: Incorrect init.d dependency info make script start to early found 541349 4.1.4+debian-2.1 user initscripts-ng-de...@lists.alioth.debian.org usertag 541349 + incorrect-dependency thanks [Andrew Chittenden] > autofs should start after nis but autofs is

Bug#541349: insserv sets the start up link for autofs to S01autofs

2009-08-13 Thread Andrew Chittenden
Package: insserv Version: 1.12.0-10 Severity: critical Justification: breaks unrelated software autofs should start after nis but autofs is being started with level 01 whereas nis is being started with level 17: # ls /etc/rc*d/*nis /etc/rc1.d/K01nis@ /etc/rc3.d/S17nis@ /etc/rc5.d/S17nis@ /etc/r