[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: environment variables
From: |
Jan-Henrik Haukeland |
Subject: |
Re: environment variables |
Date: |
Mon, 30 Jun 2003 03:54:33 +0200 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Civil Service, linux) |
Martin Pala <address@hidden> writes:
*
> I think it will be usefull to extend execution environment list (in
> spawn.c) by:
>
> MONIT_EVENT
> MONIT_SERVICE
Yes, the reason I left out MONIT_EVENT was that we do not know the
event in spawn.c. We will have to rewrite the code for this, either
use a flag in Service_T containing the current event or add the event
as a parameter to spawn(). See also my other mail on the subject and
proposal for event rewrite. MONIT_SERVICE I simply forgot :-) it
certainly should be added.
> and MONIT_ACTION (will be described in the proposal)
MONIT_EVENT sort of makes MONIT_ACTION redundant since e.g. the event
DO_STOP or the action "stop" is the same.
BTW the event DO_RESTART is ambiguous it could mean start or restart
so we should add a new event (especially if we refactor the event
model as suggested in my other mail) so we should add DO_START and let
DO_RESTART mean a real restart; that is, stop and then start.
--
Jan-Henrik Haukeland
Re: environment variables,
Jan-Henrik Haukeland <=