07-22-2008
The syntax is correct, but it seems init thinks that process is already dead and spawns a new one. If I find anything about it, I will post it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
Is it possible to add more ttys in Solaris, like with inittab in Linux? I want to switch between the ttys with Alt F1+F2+F3 .... like Linux does.
How can i do this? (1 Reply)
Discussion started by: donald1111
1 Replies
2. UNIX for Dummies Questions & Answers
Ran into a new one today at work......
I was told to start 2 servers which were shut down due to a power outage(I don't believe they were shut down incorrectly).
After fsck, both console logins appear with the message:
INIT: Command is respawning too rapidly. Check for possible errors.
>... (5 Replies)
Discussion started by: finster
5 Replies
3. UNIX for Dummies Questions & Answers
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies
4. HP-UX
INIT:Command is respawning too rapidly
Check for errors:
id:cons /usr/sbin/getty console console
A solution I read about in a different HPUX Forums help pages on line, said to add the -h option to this command in the /etc/inittab file to correct the problem.
I tried this and it did not... (2 Replies)
Discussion started by: 1bigdog
2 Replies
5. Solaris
Hi,
In Solaris 9 and below release we are using the rc script in inittab. I don't have much idea abt inittab in Solaris.
In Solris 9 and below:
We use rc3 script to start up the server. And we run database script before the rc3.
os:23:respawn:/etc/init.d/database start >/dev/null 2>&1... (7 Replies)
Discussion started by: kalpeer
7 Replies
6. Solaris
Hi,
I have a solaris 10 server,which has a process running that communicates with other system.I have made following entry in the inittab file.
PM15:s12345:respawn:/ncm/bin/communicator
PM15 : Unique process ID
s12345 : run levels
respawn : if anytime the process... (2 Replies)
Discussion started by: asalman.qazi
2 Replies
7. UNIX for Dummies Questions & Answers
Today there was a situation where processes running from inittab was broken. Can someone help me understand, how to find out, who might have stopped those processes? Or how does it get broken?
G (2 Replies)
Discussion started by: ggayathri
2 Replies
8. AIX
hello,
i have an AIX6.1.7.2 machine that it was upgraded recently from AIX5.3.9.4.
when i kill system services that should restart automatically like /usr/sbin/cron it doesnt start.
i checked my /etc/inittab file and i confirmed that this service is in respawn status so when i kill this process... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
9. UNIX for Dummies Questions & Answers
I am installing BusyBox on a device that does not have keyboard or serial connection, so I log into the system with SSH. I am in doubt about what to put in the inittab file. This is the content of the file:
::sysinit:/etc/init.d/rcS
::respawn:/bin/login
::shutdown:/sbin/swapoff -a... (1 Reply)
Discussion started by: richard78
1 Replies
10. Shell Programming and Scripting
Hi to all ,
i wrote a small script and i add it to inittab to start the script during Startup. The script works fine , if i call it from the prompt but if it is call from inittab it is runnng too but it does not recognize system variable like USER , LOGNAME.
Since i running out of ideas i... (12 Replies)
Discussion started by: Nadielosabra
12 Replies
stopped(7) Miscellaneous Information Manual stopped(7)
NAME
stopped - event signalling that a job has stopped
SYNOPSIS
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. 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.
If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job was stopped because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other
activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopped 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 after another task or service has been stopped might use:
start on stopped postgresql
SEE ALSO
starting(7) started(7) stopping(7) init(5)
Upstart 2009-07-09 stopped(7)