Surprisingly there are others too - bootlogd and tomcat for example but that doesn't make it right.
I found the following [EMAIL PROTECTED] /etc/dbus-1/event.d> ls -l total 8 -rwxr-xr-x 1 root root 1901 2006-09-20 14:15 20hal lrwxrwxrwx 1 root root 25 2006-09-28 17:52 25avahi-daemon -> ../../init.d/avahi-daemon -rwxr-xr-x 1 root root 1783 2006-09-08 12:52 70system-tools-backends and by removing that link I was able to prevent avahi coming up at boot time. So upstart is configured in basically the same way as the rcX.d system. Again, why is this necessary? With upstart you configure boot-time services with symlinks, just like the old system but in a different place. So why not do that? Here's another point, any service that behaves like this cannot be run just for the current session. You have to flip the config file, run the initscript and remember to flip the config file back again and tough luck if the service locks your machine up and you didn't get a chance to flip it off before it reboots and locks up again. This is not progress. If you're being advised that this is now "the right way to do things" I'd be happy to take this up with whoever is saying that. -- "/etc/init.d/avahi-daemon start" doesn't start anything https://launchpad.net/bugs/65587 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
