|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
[Solved] Perl, Deep recursion? exit() ignored?
Post 302889198 by zaxxon on Wednesday 19th of February 2014 10:20:39 AM
02-19-2014
|
|
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 OSF1
log
log(8) System Manager's Manual log(8) NAME
log - Records input and output from a program SYNOPSIS
/usr/sbin/log <logfile> <command> OPERANDS
The file in which to record the interaction being logged. The command to execute. DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until <command> exits, the log program exits, and the exit status of <command> is returned. The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and /var/adm/smlogs/it.log installation log files. RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation. The log program does not search for the PATH variable to locate <command> and error messages are terse. The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log foo.tmp /sbin/sh -i In the previous example, foo.tmp is the name of <logfile>. The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must exit by some other means. ERRORS
Log open error Explanation: The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly. Exec Error Explanation: The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe- cutable file. Fork Error Explanation: The log program was unable to create one of the processes it requires to log data. SEE ALSO
Commands: it(8), script(1) log(8)