Hmm, try this:
trap "" HUP works to prevent child processes dying with SIGHUP in my shell. Any more complex trap won't work, since child processes can't inherit actual shell code from the shell, just SIG_IGN.
I am trying to submit background jobs using the nohup command on a client system where my session is running under a "master shell" (BASH). If I try to nohup the actual job (ie: nohup MYJOB.BAT > MYJOB.LOG 2>&1 &) the command will fail with a return code of 126 and a "permission denied" message.... (0 Replies)
While executing a ksh file with a input parameter in background like the following
bash-2.03$nohup fil.ksh 4 &
the nohup session is stopped.
The same ksh file while executed like
bash-2.03$fil.ksh 4
works fine.
I am trying the above in Solaris 5.8 in bash shell. Please let me... (2 Replies)
Hello folks,
I have got a script which telnets to different boxes and runs a certain script with 3 run time args.
The line from the script which does it is:
(sleep 1; echo $USERID ; sleep 1; echo $PASSWD ; sleep 1 ; echo y ; sleep 1 ; echo "\r" ; sleep 1 ; echo "cd $FILEPATH" ; sleep 1 ; sleep 1... (1 Reply)
ok... want to start off by saying i am sorry for the ignorance... still trying to figure out the diffs between solaris and aix... and i think that is where i am running into problems... :o
SITTIATION:
we are doing an implementation for Oracle's CC&B... we recently switched from... (1 Reply)
Hi,
I am kinda confused with this, am not sure what is happening
i have a script say test.sh
----------
cat myfile | while read line
do
exit 2
done
echo "out of loop"
-----------
as it is evident, the exit should cause the script to terminate ,hence producing no output for the... (1 Reply)
Hello
I am running this script inst.sh
#!/bin/ksh
sqlplus -s username/password @temp.sql
----Here is my temp.sql
set serveroutput on
select instance_name from V$instance;
exit
When i run the script inst.sh on the command prompt...it runs fine...but
when i run it using... (5 Replies)
There is a daemon which is constantly writing to this particular nohup.out file.This daemon can't be stopped. But the large size of this file is hampering the directory space.I want to write a script which will wait for 48 hours and then delete the contents of the file ( nohup.out ), but not the... (1 Reply)
Hi, but it is possible to effect a sftp in???
thanks thousand
Germanico
---------- Post updated at 07:01 AM ---------- Previous update was at 05:51 AM ----------
Hi, but it is possible to effect a sftp in nohup mode??? (2 Replies)
Hi All
I am struggling to get a process to run in the background on a Ubuntu Linux machine. I run: -
/home/brad > /usr/bin/nohup sudo /home/brad/spideroak/jsystem/runner/runAgent < /dev/null &
5611
/home/brad > /usr/bin/nohup: appending output to `nohup.out'
+ Stopped (SIGTTOU) ... (9 Replies)
Hi
I need to execute about 1000 scp commands sequential , so I made "scp.sh" - like this
scp - rp ...
scp - rp ...
............
scp - rp ...
then I run
nohup sh scp.sh &The problem is: nohup process stopped when I closed session, or when the session expired,... Something wrong :(:(:(
... (4 Replies)
Discussion started by: bobochacha29
4 Replies
LEARN ABOUT DEBIAN
wdmd
WDMD(8) System Manager's Manual WDMD(8)NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if single test fails 5-6 times in row, the
watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
wdmd will exit if a watchdog driver is not loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
(Other test sources such as scripts executed each test interval may be added in the future.)
OPTIONS -D Enable debugging to stderr and don't fork.
-H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
Default 1.
2011-08-01 WDMD(8)