06-11-2007
command line
I actually meant to say "ps -e j |grep T" , T being either stopped or traced. We had a file locked open due to a suspended job running in the background which was stopped. This caused other shared sessions on the network to hang waiting for this file.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I run the top command, it shows 1 process as being Stopped. This is not a zombie, but simply a stopped process. Unfortunately, I can't figure out how to tell which process this is, nor why it is in a stopped state? Any way of finding this out? (7 Replies)
Discussion started by: IrishRogue
7 Replies
2. Shell Programming and Scripting
how to find the chid process id from given parent process id.... (the chid process doesnot have sub processes inturn) (3 Replies)
Discussion started by: guhas
3 Replies
3. UNIX for Dummies Questions & Answers
I can write a script to use ps and interigate the output, but is there a command that works similar to the find command for files where I can request a list of all the running processes over 1 day old ?
thanks! (8 Replies)
Discussion started by: MizzGail
8 Replies
4. UNIX for Advanced & Expert Users
Hi,
top process is shows like this in solaris server oracle 8i running:
load averages: 5.01, 3.35, 2.82 18:24:45
344 processes: 332 sleeping, 5 running, 2 stopped, 5 on cpu
CPU states: 22.2% idle, 29.6% user, 14.7% kernel, 33.5% iowait, 0.0% swap... (3 Replies)
Discussion started by: prakash.gr
3 Replies
5. UNIX for Advanced & Expert Users
I let a script A call script B.
I used
nohup a.sh &>/tmp/log &
In script A it calls B directly, without any redirecting or nohup or background.
However A is always "Stopped", while B is running correctly. Anybody knows why?
thanks!
-----Post Update-----
BTW, if I don't use nohup... (1 Reply)
Discussion started by: meili100
1 Replies
6. Shell Programming and Scripting
I let a script A call script B.
I used
nohup a.sh &>/tmp/log &
In script A it calls B directly, without any redirecting or nohup or background.
However A is always "Stopped", while B is running correctly. Anybody knows why?
thanks!
-----Post Update-----
BTW, if I don't use nohup... (4 Replies)
Discussion started by: meili100
4 Replies
7. UNIX for Dummies Questions & Answers
Hi. Before throwing my question, thanks to everybody for paying attention. Sorry if my english isn't good enough, but it's not my mother tongue.
That's my question:
I have a java program that throws an external program with "Process p = Runtime.getRuntime.exec(***)". The communication between... (2 Replies)
Discussion started by: jlopezperez
2 Replies
8. UNIX for Advanced & Expert Users
UNIX Tutorial Five
% kill %jobnumber
Does that not work on a stopped process? I've tried to kill a stopped process and it is not working. Or do you need a certain type of shell for this to work? I don't see anything about this in my man pages. (3 Replies)
Discussion started by: cokedude
3 Replies
9. Programming
Hi:
I have a program written in FORTRAN running on AIX platform.
It is because missing of documentation and without root password, therefore we want to modify the program so that we can find out which script/program that call this FORTRAN program.
I have google for few days, all of them are... (3 Replies)
Discussion started by: cstsang
3 Replies
10. HP-UX
Hi,
A database (Oracle) replication process was executed by the DBA team in one server (serverX). However, this replication process gets terminated, and there are no errors in the replication log. But there is error in the OS log files (syslog.log) :
Aug 8 16:51:47 L28dre02 sshd: subsystem... (1 Reply)
Discussion started by: anaigini45
1 Replies
LEARN ABOUT LINUX
starting
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)