Slight, maybe problem.

[Stu Glaser]

Could we allow services to be dependent on state?

Network is a (virtual) service, and apache should only start when the
network is running:
when network
OR
with network

This could also cause apache to stop when network is no longer running.

Allowing both state and event dependencies could also blur the line
between tasks and services.  A task depends on an event and starts
only when the event is triggered.  A service depends on a state and
can restart whenever the state requirements are satisfied.

-Stu

On 11/13/06, Scott James Remnant <scott at netsplit.com> wrote:
> My inclination is that this is mostly necessary for those combinations
> that indicate states, e.g.
>
>         from fhs-up until fhs-down and network-up until network-down
>
> That can be placed in /etc/event.d/multi-user ... then other jobs can
> refer directly to it:
>
>         with multi-user
>
> This refer could be deliberately stateful, and non-event like, so that
> it a mirroring of goals, rather than just an event trigger.