S isn't stopped. it's "interruptable sleep". Only 1 process can technically be running at a time on each CPU. T is the code you want to look out for. That means stopped by job control. see man ps for the state codes. Here's the relevant section from GNU/Linux:
This User Gave Thanks to neutronscott For This Post:
I recently encountered this on the AIX system
df command showed usage is 100% i.e 1.5 GB while du command showed usage is only 500MB
Why are the 2 commands showing different output
This command shows usage is 1.5 GB
nlxdsm29:deqadm 24> df -k .
/usr/sap/DEQ ... (3 Replies)
Hi All,
Here is my script:
sleep_time=`echo "9.6 * $num_servers"|bc| cut -d. -f1`
if ; then sleep_time=3600;fi
### Allow the compare script to kick in after 1 hour at the least
logger "Sleeping for $sleep_time seconds ...Will call compare.sh thereon" $act_log
sleep $sleep_time
#sleep... (3 Replies)
Not sure if it makes a difference but "foo" is a java process. The start time reported by various flavors of ps seems to be flopping back and forth by a minute.
I have many (a few hundred) "foo" like processes which tend to be somewhat unstable and get restarted somewhat frequently, I wrote a... (2 Replies)
Hi all,
I'm very new to unix, I'm developing an application in Java, part of which requires me to check if a certain application is still running. In windows, I just use tasklist - if the application has been shut down it won't appear in the task list. I've been trying to use the ps command to... (0 Replies)
Hi,
I have an command which find the files modified within last 8 days and then after selecting the files from the location it make the tar format and send it to the specified destination ...now I want that this task to be automative ..that is it should happen after every 5 minutes ...for that... (3 Replies)
I am trying to write my own Unix compliant (SUSv4) OS - Just a hobby OS, nothing serious. While going through the standard, I couldn't find any explicit information on process states. What I could find was (excluding the real-time considerations)-
From this it can be inferred that the... (2 Replies)
Hello,
running into a bind when im inputting the following command:
bash-3.00$ ps -p 874 -L -o pid,psr,pcpu
PID PSR %CPU
874 - 0.0
874 - 0.2
874 - 0.0
874 - 1.1
874 - 0.2
Now when i run it on my other SUN machine i get this:
bash-3.00$ ps -p 3874... (0 Replies)
My question is how would i loop a read command to keep asking the user for input and eventually print the no. of valid invalid inputs after a specified control input typed i.e. (-3). (1 Reply)
Hi Folks,
I have a situation here, where no command is giving any output, and it's not even showing any error message also.
What could be the reason? (3 Replies)
Hi All,
I have a java process which is showing high virtual memory utilization in client server. But the same process is showing comparitively lesser virtual memory consumption. I understand that virtual memory shown is not of much importance for the general user in normal condition, my client... (2 Replies)
Discussion started by: mritusmoi
2 Replies
LEARN ABOUT OPENSOLARIS
stopped
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)