Pure silence (fail)
Full spam (fail):
Meaning:
All i want to achieve is "NO 'plain-dd' output" as above, but only this part: "0 bytes (0 B) copied" so i can print it on 1 line, 'staying' that very 1 line to the user, without the console spammed.
As in $tmp contains only "20mb" -- "25mb" -- "50mb" ...
Once i could 'mute' the DD output to the user, but still retrieve the values, even with the 0+0 records, i could 'cut' it down to the value needed, but this redirection stuff drives me crazy!!
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 HPUX
proto
proto(4) Kernel Interfaces Manual proto(4)NAME
proto - prototype job file for at
SYNOPSIS DESCRIPTION
When a job is submitted to or the job is constructed as a POSIX shell script (see at(1)). The job file is created in as follows:
o creates a header describing the job as an job or a job. jobs submitted to all queues other than queue are listed as jobs. The header
is:
for an job, or
for a job.
o A set of POSIX shell commands is added to make the environment (see environ(5)) for the job the same as the current environment.
o then copies text from the prototype file to the job file, except for special variables that are replaced by other text:
Replaced by the current working directory.
Replaced by the current file size limit (see
ulimit(2)).
Replaced by the current umask (see
umask(2)).
Replaced by the time at which the job should be run,
expressed as seconds since January 1, 1970, 00:00 Coordinated Universal Time, preceded by a colon.
Replaced by text read by
from the standard input (that is, the commands provided to to be run in the job).
o When a job is submitted to queue queue, uses the file as the prototype file if it exists. Otherwise, it uses the file
EXAMPLES
The following file creates commands to change the current directory, file size limit, and umask in the job to their respective values as
they existed when was originally run. These commands are inserted before the commands in the job:
SEE ALSO at(1), queuedefs(4).
STANDARDS CONFORMANCE proto(4)