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

Re: legacy-bootordering in Wheezy?



Hi there


Tom H wrote:

You can use an insserv override to add
Should-Start: $named
Should-Stop: $named
to the nfs-kernel-server LSB headers to ensure that bind starts before nfs.

The bind9 script says: Provides:          bind9
I assume this is somehow translated into: Provides:          named.
Where can I find more on this subject.

How do I check that adding 'Should-Start: $named' and 'Should-Stop: $named' won't introduce a circular dependency?

Anyway, I haven't been able to reproducer the mentioned problem. Removing '.legacy-bootordering' did introduce this:
Dec  2 15:41:52 sput checkpc[1643]: Get_local_host: hostname 'sput' bad
Dec  2 15:41:52 sput lpd[1674]: Get_local_host: hostname 'sput' bad

Modifying /etc/host did solve this problem;
From;
192.168.1.1		sput.int.sput.nl
2001:888:1533:1::1	sput.ip6.sput.nl

To;
192.168.1.1		sput.int.sput.nl	sput
2001:888:1533:1::1	sput.ip6.sput.nl	sput

This still leaves me with my X + mouse problem.
Is there a (standard) way to run a script when starting X?


Regards,
Rob


Reply to: