One time tasks, their status and handling in upstart

Asked by Seshu Reddy Cheedepudi on 2010-12-11

Again this could be one more silly question that is already answered or documented. But as I started reading about upstart and could not find the answer (with my lazy search technique).

My question is: some tasks, for instance, the /etc/init/mountall.conf is a one time task during the boot, mount and that is it. But, initctl list/status mountall reports stopped/waiting. shouldn't it make more sense if it reports stopped/completed or similar as it does not look for a stop state/event anyway? Also, upstart can drop/ ignore parsing through the job in the list it maintains when an event occurs there after?

Question information

Language:
English Edit question
Status:
Answered
For:
upstart Edit question
Assignee:
No assignee Edit question
Last query:
2010-12-11
Last reply:
2010-12-11

Upstart doesn't know it's a "one time" task, it could be restarted at any moment

Thanks lot for the quick answer Scott. But, just to understand the upstart working mechanism. So will that have any impact on the upstart (i.e. it maintaining/listing the task through out until the system shutdown).

BTW, is upstart maintaining the event list and the corresponding jobs to be invoked (irrespective of each jobs current state, i.e. running/stopped/waiting etc) rather than maintaining the complete job list and parsing through it everytime an event occurs. I think that is kind of making sense and should not really be an overhead.

Kindly, throw some light.

Can you help with this problem?

Provide an answer of your own, or ask Seshu Reddy Cheedepudi for more information if necessary.

To post a message you must log in.