Sponsored Content
Full Discussion: MC ServiceGaurd
Operating Systems HP-UX MC ServiceGaurd Post 5055 by jwbrown on Tuesday 7th of August 2001 09:52:22 AM
Old 08-07-2001
Yes, Ober, I did post this before but did not get an answer, I couldn't find the post again to read the answer, so I thought I would try again.

I apologize for the double post.

Thank you, Michael for the info and link.

Last edited by jwbrown; 08-07-2001 at 10:56 AM..
 
starting(7)						 Miscellaneous Information Manual					       starting(7)

NAME
starting - event signalling that a job is starting SYNOPSIS
starting JOB=JOB INSTANCE=INSTANCE [ENV]... DESCRIPTION
The starting event is generated by the Upstart init(8) daemon when a new instance of a job begins starting. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs. init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs stopped by this event to be stopped before allowing the job to continue starting. This allows jobs to effectively insert themselves as dependencies of other jobs. The event is typically combined with the stopped(7) event by services. Job configuration files may use the export stanza to export environment variables from their own environment into the starting event. See init(5) for more details. EXAMPLE
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use: start on starting apache stop on stopped apache A task that must be run before another task or service is started might use: start on starting postgresql SEE ALSO
started(7) stopping(7) stopped(7) init(5) Upstart 2009-07-09 starting(7)
All times are GMT -4. The time now is 09:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy