1753261 Members
5249 Online
108792 Solutions
New Discussion юеВ

Re: No response, why?

 
SOLVED
Go to solution
papatot
Occasional Advisor

No response, why?

When I type #jobs , system no response, it soon give # prompt. Why no job IDs appear?
What jobs will appear by using this command?

Thank in advanced.
9 REPLIES 9
Steve Steel
Honored Contributor
Solution

Re: No response, why?

Hi
Maybe no active jobs. From Man sh


jobs [-lnp] [job]...

List information about each given job, or all active jobs if job
is not specified. With -l, list process IDs in addition to the
normal information. With -n, display only jobs that have stopped
or exited since last notified. With -p, list only the process
group. See the "Jobs" subsection for a description of the format
of job.


Jobs
If the monitor option of the set command is turned on, an interactive
shell associates a job with each pipeline. It keeps a table of
current jobs, printed by the jobs command, and assigns them small
integer numbers. When a job is started asynchronously with &, the
shell prints a line that looks like:

[1] 1234

indicating that job number 1 was started asynchronously and had one
(top-level) process whose process ID was 1234.

If you are running a job and wish to do something else, you can type
the suspend character (the susp character defined with stty; see
stty(1)) to send a SIGSTOP signal to the current job. The shell then
indicates that the job has been Stopped, and prints another prompt.
Then you can manipulate the state of this job by putting it in the
background with the bg command, running other commands, and eventually
returning the job to the foreground with the fg command. A suspend
takes effect immediately and resembles an interrupt, since pending
output and unread input are discarded when the suspend is entered.

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Pete Randall
Outstanding Contributor

Re: No response, why?

I think that will show any jobs you have running in background so if you have none, you will get the null response you mention.

Pete

Pete
James R. Ferguson
Acclaimed Contributor

Re: No response, why?

Hi:

If nothing appears, then nothing is running in the session's background.

Try this:

# sleep 10&
# jobs

Now wait 10-seconds and do 'jobs' again. You will not see anything.

Regards!

...JRF...
Peter Kloetgen
Esteemed Contributor

Re: No response, why?

Hi Papatot,

use the command "top" to get more information about the jobs on your system. The output has a header, which shows you the number of active processes, sleeping processes and of zombie processes. Processes are sorted by CPU consumption.

Allways stay on the bright side of life!

Peter
I'm learning here as well as helping
Wodisch_1
Honored Contributor

Re: No response, why?

Hi,

if your question is about *print* jobs then the command is "lpstat -t", else it is "ps -ef" (or even better "UNIX95=x ps -eHo pid,ppi,args").

HTH,
Wodisch
papatot
Occasional Advisor

Re: No response, why?

To Peter:
Could you tell me what's the detail difference about active processes, sleeping processes and zombie processes?

Thank you very much!
RAC_1
Honored Contributor

Re: No response, why?

Active process is the one who is taking time on cpu-doing some processing etc. Also called as run state

Sleep is the state of process where process is waiting for a call etc.

Zombie is the one that is not responding even to kernel.
There is no substitute to HARDWORK
papatot
Occasional Advisor

Re: No response, why?

Can I kill all zombie process by kill -9 ?
MANOJ SRIVASTAVA
Honored Contributor

Re: No response, why?

Genrally no as the Zombie doesnt have a valid parent ID , these porcesses can be killed if they have a valid parent ID , even thought they appear they wont consume any significant system resources .


Manoj Srivastava