Hup Post: 3879

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Hup Post 3879 by LivinFree on Thursday 12th of July 2001 09:46:08 PM

07-12-2001

Registered User

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?

LivinFree

View Public Profile for LivinFree

Find all posts by LivinFree

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

samba, swat. how to send a HUP to inetd ?

solaris can't support pkill command:(

2. Linux

syslog hup

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. UNIX for Advanced & Expert Users

Trapped Signal HUP

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. UNIX for Dummies Questions & Answers

Help with HUP and SEGV.

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...

5. Solaris

sudo for permission kill -HUP

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...

LEARN ABOUT BSD

kill

KILL(1) 						      General Commands Manual							   KILL(1)

NAME

       kill - terminate a process with extreme prejudice

SYNOPSIS

       kill [ -sig ] processid ...
       kill -l

DESCRIPTION

       Kill  sends the TERM (terminate, 15) signal to the specified processes.	If a signal name or number preceded by `-' is given as first argu-
       ment, that signal is sent instead of terminate (see sigvec(2)).	 The  signal  names  are  listed  by  `kill  -l',  and	are  as  given	in
       /usr/include/signal.h, stripped of the common SIG prefix.

       The  terminate  signal  will  kill  processes  that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
       caught.	By convention, if process number 0 is specified, all members in the process group  (i.e.  processes  resulting	from  the  current
       login)  are  signaled  (but  beware:  this works only if you use sh(1); not if you use csh(1).)	Negative process numbers also have special
       meanings; see kill(2) for details.

       The killed processes must belong to the current user unless he is the super-user.

       The process number of an asynchronous process started with `&' is reported by the shell.  Process numbers can also be found by using ps(1).
       Kill  is  a  built-in  to  csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
       arguments.  See csh(1) for details.

SEE ALSO

       csh(1), ps(1), kill(2), sigvec(2)

BUGS

       A replacement for ``kill 0'' for csh(1) users should be provided.

4th Berkeley Distribution					  April 20, 1986							   KILL(1)