One potential work-around is disabling daemonization of aiccu in its
configuration file ("daemonize false") and skipping Upstart's expect
fork altogether. aiccu (rather unfortunately) uses the daemonize flag to
determine its logging destination, but we can capture its output and log
to a file like so:exec $BIN start $DAEMON_ARGS >> /tmp/aiccu.log 2>&1 Certainly not as flexible as the syslog, but good enough for many cases. Anyone have contact with the aiccu devs? It might be simpler to request that they give users more control over aiccu's logging mechanisms instead of waiting for the Upstart devs to figure out a solution to the forking issue. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
