02-19-2014
Yep saw those useless lines and removed them (edited 1st post), but there is no difference in the behaviour.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hey Everyone,
Just starting with PERL (5.8.2) after years of KSH. Is there a way to trap the exit as you can in KSH (i.e., "trap EXIT_SCRIPT EXIT")?
Thanks in advance for any help,
gsatch (4 Replies)
Discussion started by: gsatch
4 Replies
2. Shell Programming and Scripting
I am running a korn shell script which has a recursive function.
The script ran for 117 iterations and ended up with the following error
"recursion too deep".
what should be done to avert this?
Thanks in advance
Swamy
p.s. I am on UNIX MPRAS V4 (3 Replies)
Discussion started by: swamy455
3 Replies
3. Shell Programming and Scripting
I apologize if I have already posted this query. I scanned back quite a few pages but could not find such a query.
If my perl code contains "exit(33)" how can I get that value in bash for use in a "if" statement.
Thanks,
Siegfried (5 Replies)
Discussion started by: siegfried
5 Replies
4. Shell Programming and Scripting
HI all,
can anyone tell me what does exit status 9 from perl's system function meant.
I am using system fuction to execute a shell script as :
my $s=system ('script.sh' ,arg1 ,arg2);
print $s;
the output is 9.
Thanks in advance. !!:confused: (1 Reply)
Discussion started by: glamo_2312
1 Replies
5. Shell Programming and Scripting
Hi all,
I made a simple script with a prompt menu in Perl. All working good, but I want to add an option while the program is running that on every time when the user press 'Q' the program will exit.
I know I can use $SIG{'INT'} or any other %SIG option. This option is a unix signal which I... (3 Replies)
Discussion started by: RedGrinGo
3 Replies
6. HP-UX
Hello;
Am experiencing odd problem with ssh:
=========
ssh -vvv remote_host
:
:
debug2: channel 0: rcvd adjust 65536
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0... (4 Replies)
Discussion started by: delphys
4 Replies
7. UNIX for Dummies Questions & Answers
spath="/home/user/k/${1}"
dpath="/home/user/seq/Nov17/${1}"
cd $dpath
ls -1 $spath > list
c=1
while read list
newlist=`echo $list | sed 's/.gz//' `
newnewlist=`echo $newlist | sed 's/.fastq//' `
do
echo $c
echo $list
c=$(($c+1)) (6 Replies)
Discussion started by: analyst
6 Replies
8. Shell Programming and Scripting
Im being forced to write in perl. I prefer KSH or Expect, so I suppose its time to become more fluent with perl.
I have the following problem. I want to loop through Filea and check that each line in Filea is resident in Fileb.
Filea contents
two
four
six
eight
houseboat
Fileb... (4 Replies)
Discussion started by: sumguy
4 Replies
9. Shell Programming and Scripting
Dear all,
We have a service that we start up remotely with rsh but unfortunately, the rsh never returns to the calling server. This seems to be because the processes of the service we've just started hold the port open.RBATTE1 @ /home/RBATTE1>netstat -na|grep 49.51
tcp4 0 0 ... (1 Reply)
Discussion started by: rbatte1
1 Replies
10. Programming
First time trying to work with signals in Perl.
Reviewing example I try it, but not able to get it work for 'exit'.
I hope, I am correct, assuming, that the ending any code by
exit $return_code;
the $SIG{EXIT} should be de-referenced and processed?!
So, I have such code, that, I assume,... (5 Replies)
Discussion started by: alex_5161
5 Replies
LEARN ABOUT DEBIAN
cmannotifyd
cmannotifyd(8) CMAN Notification Daemon cmannotifyd(8)
NAME
cmannotifyd - CMAN Notification Daemon
SYNOPSIS
cmannotifyd [-f] [-d]
DESCRIPTION
The cmannotifyd daemon talks to CMAN and provides a mechanism to notify external entities about cluster changes.
CMAN dispatches 3 kind of notifications:
- CMAN_REASON_TRY_SHUTDOWN when cman requests to all clients if it is allowed to shutdown.
- CMAN_REASON_STATECHANGE when cman detects a node joining or leaving the cluster.
- CMAN_REASON_CONFIG_UPDATE when a configuration change event has been detected/requested.
These notifications are then dispatched to the shell script cman_notify in the environment variable CMAN_NOTIFICATION.
cman_notify will then execute all the scripts in the configured notification directory (default: /etc/cluster/cman-notify.d) passing a very
minimal set of envvars including, of course, the CMAN_NOTIFICATION= type. The execution order is set by the filename as shown by "LC_ALL=C
ls -las".
cmannotifyd logs are stored in the default log file (/var/log/cluster/cmannotifyd.log).
cman_notify logs are stored in the default log file (/var/log/cluster/cman_notify.log). By default the output from the scripts executed by
cman_notify is redirected to /dev/null. Users can either set CMAN_NOTIFICATION_DEBUG=1 in their environment or set proper debug configura-
tion in cluster.conf to redirect scripts output to the cman_notify log file.
NOTES
cmannotifyd does not block on cman_notify nor check the exit status of the script.
Notifications are dispatched in the same order as they arrive, one by one.
CMAN_REASON_TRY_SHUTDOWN is passed to scripts for information only, they can not influence cman's decsion about whether or not to shut
down.
CMAN_REASON_STATECHANGE also implies CMAN_NOTIFICATION_QUORUM exported in the environment. CMAN_NOTIFICATION_QUORUM will be set to 1 (when
the node is part of a quorate cluster) or 0 (otherwise).
A template for cman_notify scripts can be found in the doc/ directory.
OPTIONS
-f Run in the foreground (do not fork / daemonize).
-d Enable debug output.
November 2008 cmannotifyd(8)