On Wed, Jun 04, 2008 at 01:31:20PM +0200, Frans Pop wrote: > I have been wondering why I've never seen anything from kerneloops as I > often run upstream RC kernels and have seen at least WARNON messages. > > I now find that the init script has: > # Default-Start: 3 4 5 > # Default-Stop: 0 1 2 6 > > Which means that the daemon is just not started at Debian's default > runlevel 2. I could not find any reason for that in either the man page > or in /usr/share/doc.
I guess you're using a different init system from me: /etc/rc0.d/K20kerneloops -> ../init.d/kerneloops /etc/rc1.d/K20kerneloops -> ../init.d/kerneloops /etc/rc2.d/S20kerneloops -> ../init.d/kerneloops /etc/rc3.d/S20kerneloops -> ../init.d/kerneloops /etc/rc4.d/S20kerneloops -> ../init.d/kerneloops /etc/rc5.d/S20kerneloops -> ../init.d/kerneloops /etc/rc6.d/K20kerneloops -> ../init.d/kerneloops I'll guess the reason that this is done is because the original init was done for Red Hat systems which use runlevel 2 to mean "no X", and I didn't pick up on this gratuitous and annoying difference between Debian and Red Hat. I'll fix it in the next upload, thanks for bringing it to my attention. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
