Sponsored Content
Full Discussion: Hup
Top Forums UNIX for Dummies Questions & Answers Hup Post 3836 by LivinFree on Thursday 12th of July 2001 02:19:55 AM
Old 07-12-2001
I'm curious. I was under the impression that it was simply a certain type of kill signal, in this case on a "hang up", or disconnection by the user running the process. I know certain processes restart on a HUP signal, but is that always the case, or is that simply how they handle that signal in a specific instance? For example , if I killall -HUP inetd, I know it will restart the inted daemon, re-reading all config files. But when I killall -HUP pppd, it literally hangs up...

Am I mistaken?
 

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 Replies)
Discussion started by: cloudsmell
2 Replies

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 Replies)
Discussion started by: itik
3 Replies

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 Replies)
Discussion started by: RAMESHPRABUDASS
4 Replies

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... (1 Reply)
Discussion started by: namasteall2000
1 Replies

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... (2 Replies)
Discussion started by: mohzub
2 Replies
killall(8)						      System Manager's Manual							killall(8)

NAME
killall - Terminates all processes started by the user, except the calling process SYNOPSIS
/usr/sbin/killall [- | [-]signal_name | -signal_number] /usr/sbin/killall -l FLAGS
The hyphen character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive for 30 seconds after receipt of the first signal. This gives processes that catch the SIGTERM signal an opportunity to clean up. A signal name, optionally preceded by a hyphen, sends the specified signal to processes. The hyphen character (with a signal number argument) sends the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal names and numbers, see the signal() system call. In the System V habitat, the optional signal number does not have to be preceded with a hyphen (-). Lists signal names in numerical order (as given in the /usr/include/signal.h file), stripped of the common SIG prefix. DESCRIPTION
This command provides a convenient means of killing all processes created by the shell that you control. When started by the superuser, the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes 0 and 1 (init). Security Configuration This command is modified in all security configurations of the system. EXAMPLES
To stop all background processes that have started, enter: killall This sends all background processes signal 9 (the kill signal, also called SIGKILL). To stop all background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM), waits 30 seconds, and then sends signal 9 (SIGKILL). To send a specific signal to the background processes, enter: killall -2 This sends signal 2 (SIGINT) to the background processes. To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l This displays a list of signals, which may vary from system to system. FILES
Specifies the command path RELATED INFORMATION
Calls: kill(2), sigaction(2), signal(2) delim off killall(8)
All times are GMT -4. The time now is 02:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy