07-12-2001
Well, that was only an example. Regardless, will signal 1 (HUP) always cause a process to restart, or only in some cases? I was under the impression that it killed your processes when you logged out, thus the "nohup" utility for keeping your jobs running upon logout.
For example, if I telnet to nether.net, sign in, and run "mail", it tracks my processes. Say my session is dropped, or I close my session from my end. Isn't the HUP signal sent to "mail" to kill it, as opposed to TERM(15), or INT(2)?
I know that to restart, say, inetd, for example I can kill -1 it, but not all programs follow this convention. Is that correct?
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
solaris can't support pkill command:( (2 Replies)
Discussion started by: cloudsmell
2 Replies
2. Linux
Hi All,
I modified /etc/syslog.conf and execute kill -HUP syslogd_PID. There's nothing changes on the PID when I did ps -ef|grep syslogd. It's the same. Do you think it restarted the process of syslogd?
Thanks in advance. (3 Replies)
Discussion started by: itik
3 Replies
3. UNIX for Advanced & Expert Users
We encountered an issue in our project while using the Interix UNIX (SFU 3.5) and explained our query below. We would be happy if anybody helps us to troubleshoot the problem J
In our code the trapping signal for all signals like HUP, INT, QUIT, ILL, TRAP, ABRT, EXCEPT, etc., is initialized in... (4 Replies)
Discussion started by: RAMESHPRABUDASS
4 Replies
4. UNIX for Dummies Questions & Answers
Hello - I need to know the detail of HUP and SEGV.
I know HUP is Hangup and can be use to kill a Unix login session remotely by sending a hangup signal to the process running the login session.
Could someone tell me in detail prupose of HUP and SEGV (segmentation violation)?
I need to... (1 Reply)
Discussion started by: namasteall2000
1 Replies
5. Solaris
Hi,
I'm trying to provide "/usr/bin/kill -HUP" command to one of the user using sudo file. I have configured sudo as following:
$cat /etc/sudoers
User_Alias AA=conadmin
Cmnd_Alias KILL1=/usr/bin/kill -HUPAA ALL=NOPASSWD:KILL1
When I login as the user and execute 'sudo -l' command, it... (2 Replies)
Discussion started by: mohzub
2 Replies
KILL(2) System Calls Manual KILL(2)
NAME
kill - send signal to a process
SYNOPSIS
kill(pid, sig);
DESCRIPTION
Kill sends the signal sig to the process specified by the process number in r0. See signal(2) for a list of signals.
The sending and receiving processes must have the same effective user ID, otherwise this call is restricted to the super-user.
If the process number is 0, the signal is sent to all other processes in the sender's process group; see tty(4).
If the process number is -1, and the user is the super-user, the signal is broadcast universally except to processes 0 and 1, the scheduler
and initialization processes, see init(8).
Processes may send signals to themselves.
SEE ALSO
signal(2), kill(1)
DIAGNOSTICS
Zero is returned if the process is killed; -1 is returned if the process does not have the same effective user ID and the user is not
super-user, or if the process does not exist.
ASSEMBLER
(kill = 37.)
(process number in r0)
sys kill; sig
KILL(2)