Sponsored Content
Full Discussion: Service
Operating Systems Solaris Service Post 302960498 by hicksd8 on Monday 16th of November 2015 11:16:08 AM
Old 11-16-2015
This service is the Hardware Management Agent.

What hardware platform is this?

Are you running in an ESX environment?

Have you applied any patches/upgrades recently?

When was it last starting okay? Or never?
 

3 More Discussions You Might Find Interesting

1. HP-UX

Service Guard

Hi admins, I need some help writing functional specifications for planning a two nodes Service Guard Cluster. Can anybody help me thanks at advance (1 Reply)
Discussion started by: hmaiida
1 Replies

2. HP-UX

Background service!

Hi I'm wondering, Is there a way to run an application as a background service on HP-UNIX? I'm a complete noobie! Basically I got an application that runs as an NT service on windows. This application is cross-platform and I am wondering if I could run it as some background service on HP-unix... (2 Replies)
Discussion started by: jun27
2 Replies

3. UNIX for Beginners Questions & Answers

Run one service after another service has finished - systemd

Hi all I would like to know how to run task2.service after task1.service has finished. task1.service has a timer (task1.timer), that makes it run every 5 minutes OnCalendar=*:0/5task2.service is basically a script, that has to work on the files created after task1 has finished. This is what I... (2 Replies)
Discussion started by: guilliber
2 Replies
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 06:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy