If I read your reply correctly, I think you want to throw away all the output, not have it written to nohup.out.
If you use nohup then the only way to stop it creating a nohup.out file is to make sure you redirect both stdout and stderr to somewhere else. So for instance if your script was called 'run_sample.sh' you would use:
If this is not what you want then please explain again.
I am newbie to unix shells world.
I am trying to capture a background process id into a file so that it can be killed later.
this process is basically a java program running in background as:
java TestApp &
this returning process id immediately. So how can i redirect that pid into a file.... (1 Reply)
Hello all,
I would be happy if any one could help me with a shell script that would determine all the processes running on a Unix server and post a mail if any of the process is not running or aborted.
Thanks in advance
Regards,
pradeep kulkarni.
:mad: (13 Replies)
Guys
we all know what command 'COLUMNS=2047 /usr/bin/ps –eo pid,ppid,uid,user,args' does.It prints 5-column output for the running processes on a AIX box.
Here is simple thing i need:
I need to insert this tabular data in a db2 table.
How do i need?
I have created table with these five... (0 Replies)
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
i'm looking to have my script capture it's own process name while running.
i'm going to use this in the output of the script to track which script produced which output file(s).
when i run:
ps -ef | grep processname
i only get as results a ps -ef listing for the grep inside my... (6 Replies)
Hi,
I just wonder I need to write a script where I can check if a particular process is consuming X amount of CPU. I was thinking of using the ps command but doesn't seems to work. Any ideas. Thanks. (2 Replies)
Hi,
I'm gonna launch a process from my 'C' code. I'm gonna launch it a few times. I would like to capture the PID of that process each time I launch. I have to copy the each PIDs into a 'C' variable and I have to kill all of them when I exit from the 'C' code.
My requirement is
int... (3 Replies)
I have two set of questions.
1) To skip killing some process automatically.
2) To kill other process and capture their log.
I have set of process, some needs to be killed gracefully and others should be skipped.
Listed are the process.
adm 1522... (1 Reply)
Hi All,
I was out not working on unix from quite sometime and came back recently. I would really appreciate a help on one of the issue I am facing....
I am trying to kick off the CodeNameProcess.sh in PARALLEL for all the available codes. The script runs fine in parallel.
Let say there are... (1 Reply)
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Discussion started by: shunya
5 Replies
LEARN ABOUT FREEBSD
nohup
NOHUP(1) BSD General Commands Manual NOHUP(1)NAME
nohup -- invoke a utility immune to hangups
SYNOPSIS
nohup [--] utility [arguments]
DESCRIPTION
The nohup utility invokes utility with its arguments and at this time sets the signal SIGHUP to be ignored. If the standard output is a ter-
minal, the standard output is appended to the file nohup.out in the current directory. If standard error is a terminal, it is directed to
the same place as the standard output.
Some shells may provide a builtin nohup command which is similar or identical to this utility. Consult the builtin(1) manual page.
ENVIRONMENT
The following variables are utilized by nohup:
HOME If the output file nohup.out cannot be created in the current directory, the nohup utility uses the directory named by HOME to create
the file.
PATH Used to locate the requested utility if the name contains no '/' characters.
EXIT STATUS
The nohup utility exits with one of the following values:
126 The utility was found, but could not be invoked.
127 The utility could not be found or an error occurred in nohup.
Otherwise, the exit status of nohup will be that of utility.
SEE ALSO builtin(1), csh(1), signal(3)STANDARDS
The nohup utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BUGS
Two or more instances of nohup can append to the same file, which makes for a confusing output.
BSD July 19, 2001 BSD