Excerpts from codewarrior's message of Wed Apr 27 08:18:28 UTC 2011:
> I completely agree, this patch is not the final solution - it's just a
> 'sticking plaster'. Better solutions must include changes to Upstart
> which ultimately must handle system shutdown internally. Maybe there's
> a case for adding a shutdown event which then blocks new services &
> tasks from starting (like shutdown does for logins) and enforces the
> kill timeout.
>
> I would hate to see a system shutdown 'hanging' in a recovery shell
> simply because of a few open files. Umount must be made more resilient
Excerpts from codewarrior's message of Wed Apr 27 08:18:28 UTC 2011:
> I completely agree, this patch is not the final solution - it's just a
> 'sticking plaster'. Better solutions must include changes to Upstart
> which ultimately must handle system shutdown internally. Maybe there's
> a case for adding a shutdown event which then blocks new services &
> tasks from starting (like shutdown does for logins) and enforces the
> kill timeout.
>
> I would hate to see a system shutdown 'hanging' in a recovery shell
> simply because of a few open files. Umount must be made more resilient