You guys probably knew already, but me just figured out how to get the return value of job running/ran in background.
For some weird reason it didnt want to work with an exported variable.
This one will write the exit code to a temp file, so it can be easy retrieved after the loop is done.
Where $JOB is a scriptfile containg the command to execute and $TEMP_FILE is a pre-set var (like: /tmp/tmp.ret)
Now to use that retvar in a variable again is easy:
Et voila
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
Hi all,
I am running a job .. and i want to know the status tht it is runnig or not ..
and how can i find the jobId of my job ..
I have to get it to kill my running job
Pls let me know da Unix commands to do it ..
i m wrking on Hp UNIX (1 Reply)
I have run one shell script in background that contains a endless while loop.
I am not able to know the status of that job .
Please provide any command to know this. I have already used "ps -aef" , "jobs" to know it , but it didn't work. I am sure the process is running as it is generating a file... (8 Replies)
Guys,
We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem.
Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run.
... (2 Replies)
Hello,
I am running a shell script whose execution often takes several hours to complete. Is there way I can get some kind of status update as the job is running? Something as simple as the start and the current time stamp.
Thanks,
Gussi (2 Replies)
Hi All,
I have a scenario where I am executing some child shell scripts in background (using &)through a master parent script.
Is there a way I can capture the exit status of each individual child script after the execution is completed. (2 Replies)
Is there a way to suspend (TSTP?) a job that is running in the background, _without_ first bringing it to the foreground and inputting Ctrl-Z from the keyboard?
IOW, something similar to issuing the shell's bg builtin command on a job ID to resume a job that is suspended in the background,... (2 Replies)
Hi,
Should the user jobs specified in crontab be running in background?
Cron daemon is already running in background. So I am not sure
whether should the jobs (output and error messages are redirected to file)
ran by it be explicitly stated to be run in background (& at end of command)
if one... (1 Reply)
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Discussion started by: ketanraut
9 Replies
LEARN ABOUT ULTRIX
lpq
lpq(1) General Commands Manual lpq(1)Name
lpq - spool queue examination program
Syntax
lpq [ options ] [ job #... ] [ user... ]
Description
The command examines the spooling area used by for printing files on the printer, and reports the status of jobs. The command invoked
without any arguments reports on any jobs currently in the default queue.
When jobs are being printed, reports the queue as being ``active''. For each job submitted, reports the user's name, current rank in the
queue, the names of files comprising the job, the job identifier and the total size in bytes. The job identifier is a number which may be
supplied to to remove a specific job.
Job ordering is determined by the FIFO (First In, First Out) algorithm used to scan the spooling directory. When the queue is empty,
reports that there are ``no entries''.
File names may be unavailable for some jobs, for example, if the command is used without specifying a file name, or if is used in a pipe
line. If file names are unavailable, the file name reported by is ``standard input''.
Arguments
job #... Causes to report on only the job number(s) specified.
user... Causes to report on only the jobs for the specified user(s).
Options
+n Scan and display the spool queue until the queue is empty. The queue is scanned every n seconds, if no argument is specified the
queue is scanned every 30 seconds.
-l Display the status of each job on more than one line if necessary. If this option is not used, the status of each job is displayed on
one line.
-Pprinter
Report the status of the spool queue for the printer specified. If this option is not used, the spool queue displayed is the one
defined by the PRINTER environment variable. If a queue is not defined by the PRINTER environment variable, the spool queue displayed
is for the printer named ``lp'' in the file.
Restrictions
The displayed status of the spool queue may not always be the current status. This is because jobs may be completed after the queue has
been examined, but before the status has been displayed.
Error Messages
Two of the most common error messages from are:
Warning: no daemon present (R)
A daemon is not available for the specified printer. Refer to the command to find out how to restart the printer daemon.
unknown printer (R)
The printer specified as an argument to the -P option, doesn't have an entry in the file.
Files
For manipulating the screen for repeated display
To determine printer characteristics
The spooling directory, as determined from printcap
Control files specifying jobs
The lock file to obtain the currently active job
See Alsolpr(1), lprm(1), lpc(8), lpd(8)lpq(1)