Comment 9 for bug 688541

2010/12/14 Clint Byrum <email address hidden>:
>
> I do think the appropriate fix is to have umountfs emit an 'unmounting-
> filesystems' event and anything that does a 'start on local-filesystems'
> or 'start on filesystem' should also 'stop on unmounting-filesystems',

What do you do about services which have
"start on runlevel [2345]" and the binary is in /usr?

There are quite a few examples here: acpid, atd, cron, irqbalance, etc
which all have:

start on runlevel [2345]
stop on runlevel [!2345]

Either those jobs are buggy to not specify the "start on
(local-)filesystems" dependency or your criteria is not sufficient.

Imho the major problem here is, that there is a mixup between
dependencies that need to be satisfied to be able to run a job and
when (in which runlevels) to start a job.

Michael

--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?