I' m note very expert in the reliable manage of signal... but in my server I must manage SIGPIPE for the socket and SIGTERM...
I've wrote this but there is something wrong... Can someone explain me with some example the reliable management of signal??
You should proceed as follows:
for SIGPIPE: you usually want to set to ignore SIGPIPE. Advantage: you will be synchronously informed in the send() function if a SIGPIPE is caught (return -1, and errno is set to EPIPE). No need to mess up with a signal handler.
for SIGTERM, set simply a signal handler with sigaction()
This simply looks like this:
In particular, don't use sigprocmask. You would block the signal SIGTERM and SIGPIPE, preventing effectively your handlers to run!
Hi all,
I need some urgent help.
we are using Dynix/ptx V4.5 on i386, have several processes and instances are running on the box round the clock.we increased the processes recently.
We have coded to handle the signals in our programs.
Recently, we noticed most of our processes are... (2 Replies)
Hi folks,
Can anyone assist with pointers for the following snag?
We have custom method (IBM-supplied) for running the audit subsystem on 5.1-07
/etc/security/audit objects, events and config have been edited, and the /etc/security/audit/streamcmds contains the following routine;
... (1 Reply)
Dear All
We have JBOSS server running on Linux we need to track Graceful Shutdown(SIGTERM) and Forceful Shutdown(SIGKILL) timestamp and write it into one file, I am new to UNIX Signal processing if is it possible how to detect it?
We generally do
$kill PID For Graceful... (5 Replies)
catch signal SIGPIPE ,print errno but it's value equal to 2(ENOENT)
#define ENOENT 2 /* No such file or directory */
is it should be EPIPE ?
#define EPIPE 32 /* Broken pipe */
Thanks ! (7 Replies)
Hi
This is a exercise question from Unix network programming vol2.
Why the SIGPIPE signal is generated only for writers when readers disappear.
why not it is generated for readers when writer disappears.
I guess, if the writer didn't get any response like the reader gets EOF,
it will... (4 Replies)
When a write() writes on a broken pipe, with no readers, it generates a SIGPIPE signal and the process exits.
When the write() returns -1 and errno is EPIPE?
Do I have an handler for SIGPIPE, or can I ignore it? (2 Replies)
edit by bakunin: content not relevant for our site (and bordering on spam) SNIPped, thread closed.
My suggestion is to - before even considering to buy anything online - put more effort in research, i.e. what the web site you write a comment at, is all about. This one here is definitely not for... (1 Reply)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
We must do the following for a massive coding project that is due at 12:20PM on Monday, July 22, 2013. We are to... (1 Reply)
I have 2 AIX 6.1 systems running on PowerPCs - production and .. .everything else. :p . Until the installation of a TLS certificate in an application, some copying of files ("cloning an environment") and upgrading a listener, sending a kill -15 worked on any script/application, so long as we were... (6 Replies)
Discussion started by: Mrucker
6 Replies
LEARN ABOUT FREEBSD
timeout
TIMEOUT(1) BSD General Commands Manual TIMEOUT(1)NAME
timeout -- run a command with a time limit
SYNOPSIS
timeout [--signal sig | -s sig] [--preserve-status] [--kill-after time | -k time] [--foreground] <duration> <command> <args ...>
DESCRIPTION
timeout starts the command with its args. If command is still running after duration, it is killed. By default, SIGTERM. is sent.
--preserve-status Always exits with the same status as command even if it times out.
--foreground Do not propagate timeout to the command children.
-s sig, --signal sig Specify the signal to send on timeout. By default, SIGTERM. is sent.
-k time, --kill-after time Send a second kill signal if command is still running after time after the first signal was sent.
DURATION FORMAT
duration and time can be integer or decimal numbers. Values without unit symbols are interpreted as seconds.
Supported unit symbols are:
s seconds
m minutes
h hours
d days
EXIT STATUS
If the timeout was not reached, the exit status of command is returned.
If the timeout was reached and --preserve-status is set, the exit status of command is returned. If --preserve-status is not set, an exit
status of 124 is returned.
If command exits after receiving a signal, the exit status returned is the signal number plus 128.
If command is an invalid command, the exit status returned is 126.
If command is a non existing command, the exit status returned is 127.
If an invalid parameter is passed to -s or -k, the exit status return is 125.
SEE ALSO kill(1), signal(3)BSD Oct 28, 2014 BSD