2010/12/10 Ante Karamatić <email address hidden>:
> Suggestion: make umountfs wait for all upstart jobs to finish.
Doesn't that conflict though with what is written in /etc/init.d/sendsigs:
# Upstart jobs have their own "stop on" clauses that sends
# SIGTERM/SIGKILL just like this, so if they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid"
done
or
# did an upstart job start since we last polled initctl? check
# again on each loop and add any new jobs (e.g., plymouth) to
# the list. If we did miss one starting up, this beats waiting
# 10 seconds before shutting down.
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid" done
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
2010/12/10 Ante Karamatić <email address hidden>:
> Suggestion: make umountfs wait for all upstart jobs to finish.
Doesn't that conflict though with what is written in /etc/init. d/sendsigs:
# Upstart jobs have their own "stop on" clauses that sends
OMITPIDS= "${OMITPIDS: +$OMITPIDS }-o $pid"
# SIGTERM/SIGKILL just like this, so if they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do
done
or
# did an upstart job start since we last polled initctl? check
OMITPIDS= "${OMITPIDS: +$OMITPIDS }-o $pid"
done
# again on each loop and add any new jobs (e.g., plymouth) to
# the list. If we did miss one starting up, this beats waiting
# 10 seconds before shutting down.
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?