| The man page for nohup mentions two possible areas to watch for ...
:
If nohup output is redirected to a terminal or is not redirected at
all,
the output is appended to the file nohup.out. If the file is
created, the
permission bits are set to Owner Read and Owner Write (600). If
nohup.out
is not writable in the current directory, the output is redirected to
$HOME/nohup.out. If neither file can be created nor opened for
appending,
utility is not invoked.
:
The csh command contains a built-in subcommand named nohup. The
command
and subcommand do not work the same way. For information on the csh
built-in subcommand, see the csh command. To invoke the nohup
command, use
an absolute path (for example /usr/bin/nohup).
:
So first you need to work out which nohup your customer is using.
# which nohup
may return either /usr/ucb/nohup or builtin/nohup
Then check to see if _exactly_ what your customer is doing, and whether
or not he has a need to write to nohup.out
And if you haven't already done it, check that his Oracle script
actually works independantly from nohup.
Hope tihs helps
leon
|