[Bug 1015223] Re: cloud-init-nonet main process killed by TERM signal

Clint Byrum clint at fewbar.com
Tue Jun 19 21:28:42 UTC 2012


I'm adding an upstart task. I'm wondering if its even valid for upstart
to log these at the default log priority. Perhaps they should be dropped
to 'info' level. Killing a process as part of stopping the job is a
perfectly normal situation and doesn't really seem to warrant logs. The
only time I think it might be useful is when debugging issues with boot
ordering, which would seem to be a good time to lower log priority to
info anyway.

** Also affects: upstart (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223

Title:
  cloud-init-nonet main process killed by TERM signal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1015223/+subscriptions



More information about the Ubuntu-server-bugs mailing list