im trying to make a trap signal 2 (ctrl c) in a bash script
if a user presses ctrl c while running the script it should display an error message but not quit the bash script just yet. User will have to press "enter" to quit
I wrote a ksh script for Helpdesk. I need to know how to disable ctrl-c,ctrl-z,ctrl-d..... so that helpdesk would not be able to get to system prompt :confused: (6 Replies)
Hello
I have a master startup script (let's call it myScript) that displays a menu from which the user can start/stop several instances of a server. When I issue the start command for one of the servers from the menu and then exit myScript through the provided mechanism (enter "q" in this case),... (2 Replies)
Hi there,
I'm using HP-UX 11 machine. I am running a script, thats gonna take a long time to execute. When I press ctrl-c to come out of my script, I have to catch that signal(ctrl-c) and display that ctrl-c had been pressed. How can I do it.
Thanks in advance (2 Replies)
hi all....
plz tel me how can i solve this....here's the situation (just a sample!!)..
$ cat sigtrap
#!/usr/bin/perl
$SIG{'INT'} = 'ABORT';
sub ABORT {
print "\nStop the loop?? (y/n) : ";
chop($ch=<STDIN>);
if ($ch =~ //)
{
... (3 Replies)
H! I have written script where it need to invoke the perl script in background, then write the pid in temp file then bring back the job to foreground. whenever the Ctrl-C or Ctrl-Z is pressed in the script has to exit and prompt should be dispalyed. but this script causing exit from shell session... (2 Replies)
Hi,
while executing shell script, in the middle of the process, if we kill the shell script( ctrl+z or ctrl+c), script will be killed and the files which using for the script will be in the folder.
How to handle those scenarios. Is there any possibilities, if user breaks the script, I need to... (3 Replies)
Hi friends,
I am trying to add a newline char ('\n') between the query and the commit statement in the following shell script.
#! /bin/sh
echo "select * from tab; commit;" > data.sql
I have tried typing in "Ctrl-V + Ctrl-J" combination which has inserted ^@ (NUL) character but the commit... (1 Reply)
Hi Experts,
Is it possible to send ctrl + d signal from a inside a file made with vi, using Ctrl V , Esc and 004 , escape sequence.
Since : 004 should exit the script if executed. Is this something possible.
I am trying with vi , I put this code ^ , and trying to execute it but... (4 Replies)
Hi..!
I'm stuck with my automation of starting a process and keeping it running even after the current ssh session has exited..
So i'm trying to use command 'screen'. which is doing exactly what i wanted, But the problem is automation of the same.
i will have to press Ctrl+a and Ctrl+d for... (2 Replies)
fiu-ctrl(1) General Commands Manual fiu-ctrl(1)NAME
fiu-ctrl - a script to remote control programs using libfiu
SYNOPSIS
fiu-ctrl [options] PID [PID ...]
DESCRIPTION
fiu-ctrl is a script to enable/disable failure points in running programs that are using libfiu(3).
Programs are usually launched using fiu-run(1), which enables libfiu's remote control capabilities without the need to modify the program's
code.
For additional documentation, go to the project's website at http://blitiri.com.ar/p/libfiu.
OPTIONS -c command
Run the given libfiu remote control command before executing the program (see below for reference).
-f ctrlpath
Set the default prefix for remote control over named pipes. Defaults to "$TMPDIR/fiu-ctrl", or "/tmp/fiu-ctrl" if "$TMPDIR" is not
set, which is the usually correct for programs launched using fiu-run(1).
Remote control commands are of the form "command param1=value1,param2=value2". Valid commands are:
'enable name=NAME'
Enables the NAME failure point unconditionally.
'enable_random name=NAME,probability=P'
Enables the NAME failure point with a probability of P.
'disable name=NAME'
Disables the NAME failure point.
All of the enable* commands can also optionally take failnum and failinfo parameters, analogous to the ones taken by the C functions.
EXAMPLES
The following command will tell the process running with PID 12345 to enable the failure point posix/io/read with a 25% of probability to
fail, and the failure point libc/mm/malloc with a 5% of probability to fail:
fiu-ctrl -c 'enable_random name=posix/io/*,probability=0.25'
-c 'enable_random name=libc/mm/*,probability=0.05' 12345
And the following will tell the same process to disable the previously enabled failure point posix/io/read:
fiu-ctrl -c 'disable name=posix/io/read' 12345
SEE ALSO libfiu(3), fiu-run(1).
BUGS
If you want to report bugs, or have any questions or comments, just let me know at albertito@blitiri.com.ar. For more information about
libfiu, you can go to http://blitiri.com.ar/p/libfiu.
16/Jun/2009 fiu-ctrl(1)