Excerpts from Jeroen Massar's message of Wed Jul 13 10:53:00 UTC 2011: > > Jeroen, his upstart job does not use the 'respawn' keyword, so it will not > > be "automatically restarted" like daemontools does. > > This is only started when there is a real network interface (something I > > would think necessary for this daemon to work!), > > and stopped when the system is going down. > > I agree that bringing the daemon up when the network goes up is fine, > and as there is a PID file it will only run once and not start again > when the interface is brought up again. > > Stopping it when the network goes down though will mean that when the > network is flipping (which we have seen at several people already) you > will be effectively start/stopping the daemon all the time.
It does no such thing. It stops on runlevel [^2345].. which basically means any time the system goes into a 'rebooting', 'shutting down' or 'single user maintenance mode' state. Also local-filesystems only happens during bootup, so it will effectively only be started automatically at bootup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/223825 Title: aiccu init.d script will race dhclient (upstart issue?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/223825/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
