Sponsored Content
Top Forums Shell Programming and Scripting how to ignore control commands Post 35593 by google on Sunday 20th of April 2003 08:23:03 PM
Old 04-20-2003
see 'man trap'

also search the forum for keywords such as signals, trap, INT, HUP KILL
 

10 More Discussions You Might Find Interesting

1. Programming

code that reads commands from the standard i/p and executes the commands

Hello all, i've written a small piece of code that will read commands from standard input and executes the commands. Its working fine and is execting the commands well. Accepting arguments too. e.g #mkdir <name of the directory> The problem is that its not letting me change the directory i.e... (4 Replies)
Discussion started by: Phrozen Smoke
4 Replies

2. UNIX for Dummies Questions & Answers

please ignore this....

Most of the people think that they can not use Unix as desktop. By this poll we gone tell them that we not just use Unix as desktop but also love different display managers like GNOME, KDE etc..... (1 Reply)
Discussion started by: ynilesh
1 Replies

3. UNIX for Advanced & Expert Users

can some one give me some link about process and job control commands

can some one give me some link about process and job control commands (2 Replies)
Discussion started by: alokjyotibal
2 Replies

4. Shell Programming and Scripting

Can BASH execute commands on a remote server when the commands are embedded in shell

I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config. I am not sure if I can do this with BASH scripting. I have set up password less login by adding my public key to authorized_keys file, it works. I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies

5. Shell Programming and Scripting

How to ignore STDERR when nesting commands?

I have a pel script running as root that needs to read the contents of a file on a remote system, I have an ssh trust relationship as a particular user but not as root. I then need to write back out to that file again to change it's content a bit. On the surface this seemed really easy but... (3 Replies)
Discussion started by: Smiling Dragon
3 Replies

6. Shell Programming and Scripting

ls ignore pattern

Hi, I have a FTP script that check for ".done" files in the remote path and the "get" the corresponding data files. Here's how it does..... First it list all the *.done file as below: ls *.done And then it picks one file and get the corresponding data file. After that it... (3 Replies)
Discussion started by: dips_ag
3 Replies

7. Shell Programming and Scripting

Getting ls to ignore ~ and # files

Is there a way to customize ls to ignore files ending with ~ and #? (those are Emacs backup and auto-save files). I found -B option, which only ignores ~ files (2 Replies)
Discussion started by: yaroslavvb
2 Replies

8. AIX

HACMP: difference between 'cl' commands and 'cli' commands

Hi all, I'm new in this forum. I'm looking for the difference between the HACMP commands with the prefix "cl" and "cli". The first type are under /usr/es/sbin/cluster/sbin directory and the second are under /usr/es/sbin/cluster/cspoc directory. I know that the first are called HACMP for AIX... (0 Replies)
Discussion started by: peppix
0 Replies

9. UNIX for Advanced & Expert Users

Ignore .profile

hi there i try to login on a remote system without running the .profile of the remote user. is there a way to do that? can i just ignore it or can i tell the ssh command wich .profile to use? thanks for your help. cheers, zeroone (1 Reply)
Discussion started by: zeroone
1 Replies

10. Solaris

Help needed - trying to run commands in Guest LDoms from Control LDOM

Hi Folks, I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level. Can the same be done with Guest LDoms while remaining at the control LDOM level? ... (4 Replies)
Discussion started by: momin
4 Replies
sigtrap(3pm)						 Perl Programmers Reference Guide					      sigtrap(3pm)

NAME
sigtrap - Perl pragma to enable simple signal handling SYNOPSIS
use sigtrap; use sigtrap qw(stack-trace old-interface-signals); # equivalent use sigtrap qw(BUS SEGV PIPE ABRT); use sigtrap qw(die INT QUIT); use sigtrap qw(die normal-signals); use sigtrap qw(die untrapped normal-signals); use sigtrap qw(die untrapped normal-signals stack-trace any error-signals); use sigtrap 'handler' => &my_handler, 'normal-signals'; use sigtrap qw(handler my_handler normal-signals stack-trace error-signals); DESCRIPTION
The sigtrap pragma is a simple interface to installing signal handlers. You can have it install one of two handlers supplied by sigtrap itself (one which provides a Perl stack trace and one which simply "die()"s), or alternately you can supply your own handler for it to install. It can be told only to install a handler for signals which are either untrapped or ignored. It has a couple of lists of signals to trap, plus you can supply your own list of signals. The arguments passed to the "use" statement which invokes sigtrap are processed in order. When a signal name or the name of one of sigtrap's signal lists is encountered a handler is immediately installed, when an option is encountered it affects subsequently installed handlers. OPTIONS
SIGNAL HANDLERS These options affect which handler will be used for subsequently installed signals. stack-trace The handler used for subsequently installed signals outputs a Perl stack trace to STDERR and then tries to dump core. This is the default signal handler. die The handler used for subsequently installed signals calls "die" (actually "croak") with a message indicating which signal was caught. handler your-handler your-handler will be used as the handler for subsequently installed signals. your-handler can be any value which is valid as an assignment to an element of %SIG. See perlvar for examples of handler functions. SIGNAL LISTS sigtrap has a few built-in lists of signals to trap. They are: normal-signals These are the signals which a program might normally expect to encounter and which by default cause it to terminate. They are HUP, INT, PIPE and TERM. error-signals These signals usually indicate a serious problem with the Perl interpreter or with your script. They are ABRT, BUS, EMT, FPE, ILL, QUIT, SEGV, SYS and TRAP. old-interface-signals These are the signals which were trapped by default by the old sigtrap interface, they are ABRT, BUS, EMT, FPE, ILL, PIPE, QUIT, SEGV, SYS, TERM, and TRAP. If no signals or signals lists are passed to sigtrap, this list is used. For each of these three lists, the collection of signals set to be trapped is checked before trapping; if your architecture does not implement a particular signal, it will not be trapped but rather silently ignored. OTHER untrapped This token tells sigtrap to install handlers only for subsequently listed signals which aren't already trapped or ignored. any This token tells sigtrap to install handlers for all subsequently listed signals. This is the default behavior. signal Any argument which looks like a signal name (that is, "/^[A-Z][A-Z0-9]*$/") indicates that sigtrap should install a handler for that name. number Require that at least version number of sigtrap is being used. EXAMPLES
Provide a stack trace for the old-interface-signals: use sigtrap; Ditto: use sigtrap qw(stack-trace old-interface-signals); Provide a stack trace on the 4 listed signals only: use sigtrap qw(BUS SEGV PIPE ABRT); Die on INT or QUIT: use sigtrap qw(die INT QUIT); Die on HUP, INT, PIPE or TERM: use sigtrap qw(die normal-signals); Die on HUP, INT, PIPE or TERM, except don't change the behavior for signals which are already trapped or ignored: use sigtrap qw(die untrapped normal-signals); Die on receipt one of an of the normal-signals which is currently untrapped, provide a stack trace on receipt of any of the error-signals: use sigtrap qw(die untrapped normal-signals stack-trace any error-signals); Install my_handler() as the handler for the normal-signals: use sigtrap 'handler', &my_handler, 'normal-signals'; Install my_handler() as the handler for the normal-signals, provide a Perl stack trace on receipt of one of the error-signals: use sigtrap qw(handler my_handler normal-signals stack-trace error-signals); perl v5.16.2 2012-10-11 sigtrap(3pm)
All times are GMT -4. The time now is 03:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy