When SIGINT is delivered for the first time, shouldn't the handler code be executed and its action default to SIG_DFL of SIGINT so that the next time when SIGINT is delivered it should logically terminate
Its not happening so,
each time a SIGINT is delivered, handler is executing without any problems.
Any idea to repeat an action to all the lines in vi...
suppose i want to delete the first word from all the lines in VI .. how would i do it ?
in general i am also looking for a way to apply a action to all the lines in VI . (6 Replies)
Hi..
When i refered the script /etc/rc.sysinit...
i found the "action commands" like
But this is not working in my shells..
the following error is coming...
Please anybody help
Thanks in advance
esham (5 Replies)
in /etc/init.d/networking of an ubuntu computer, I found this code:
if ifdown -a --exclude=lo; then
log_action_end_msg $?
else
log_action_end_msg $?
fi
Shouldn't it be replace by
ifdown -a --exclude=lo
... (0 Replies)
I am writing a shell script that takes at least 2 arguments. The first is an octal representation of file permissions, the second is a command that is executed on all the files found with that permission.
#!/bin/sh
find . -perm $1 -exec $2 $3 $4 {} \;
invoked: ./script.sh 543 ls -la
what... (3 Replies)
Hello,
One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1.
On AIX 5.3, there were no issues.
Here is the truss output.
811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884... (0 Replies)
lets explain it easy by showing the initial file and desired file:
I've a file such this that contains:
initial_file:
31/12/2011 23:46:08 38.6762 43.689 14.16 Ml 3.1
... (1 Reply)
Discussion started by: oreka18
1 Replies
LEARN ABOUT MOJAVE
bsd_signal
BSD_SIGNAL(3) BSD Library Functions Manual BSD_SIGNAL(3)NAME
bsd_signal -- simplified signal facilities
SYNOPSIS
#include <signal.h>
void (*
bsd_signal(int sig, void (*func)(int)))(int);
or in an equivalent but easier to read typedef'd version:
typedef void (*sig_t) (int);
sig_t
bsd_signal(int sig, sig_t func);
DESCRIPTION
The bsd_signal() function provides a partially compatible interface for programs written to historical system interfaces (see USAGE below).
The function call bsd_signal(sig, func) has the effect as if implemented as:
void (*bsd_signal(int sig, void (*func)(int)))(int)
{
struct sigaction act, oact;
act.sa_handler = func;
act.sa_flags = SA_RESTART;
sigemptyset(&act.sa_mask);
sigaddset(&act.sa_mask, sig);
if (sigaction(sig, &act, &oact) == -1)
return(SIG_ERR);
return(oact.sa_handler);
}
The handler function should be declared:
void func(int sig)
where sig is the signal number. The behavior is undefined if func() is a function that takes more than one argument, or an argument of a
different type.
RETURN VALUES
Upon successful completion, bsd_signal() returns the previous action for sig. Otherwise, SIG_ERR is returned and errno is set to indicate
the error.
ERRORS
Refer to sigaction(2).
USAGE
This function is a direct replacement for the BSD signal(3) function for simple applications that are installing a single-argument signal
handler function. If a BSD signal handler function is being installed that expects more than one argument, the application has to be modi-
fied to use sigaction(2). The bsd_signal() function differs from signal(3) in that the SA_RESTART flag is set and the SA_RESETHAND will be
clear when bsd_signal() is used. The state of these flags is not specified for signal(3).
SEE ALSO sigaction(2), sigaddset(3), sigemptyset(3), signal(3)STANDARDS
The bsd_signal() function conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BSD December 20, 2003 BSD