11-06-2002
Not exactly sure what you are asking, but have you tried kill -HUP. Another usefull resource may be the signal man page (man -s 3HEAD signal to get to it on most systems).
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am curious about HUP..... kill -HUP pid
What exactly does it do?? Does it stop the process and restart it from the beginning or from where it stopped? Thanks (6 Replies)
Discussion started by: jwbrown
6 Replies
2. SuSE
everytime I try to start SWAT using : www.localhost:901, it takes me to goggle the search engine. IM still new in the linux world and Im a bit confussed now. any help would be great. Im currently running redhat linux fedora. (5 Replies)
Discussion started by: keliy1
5 Replies
3. Solaris
Hi,
I had define swat in /etc/services, in /etc/inet/inetd.conf. When I start swat http://localhost:901 I receive the follow message: ld.so.1: swat: fatal: libiconv.so.2: open failed: No such file or directory
Then I restart the system and the same message is comming. The swat is only... (2 Replies)
Discussion started by: MuellerUrs
2 Replies
4. 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
5. 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
6. 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
7. 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
8. Red Hat
Hi,
I have installed RHEL 5.2 for a specific reason.
Anyway I would really like to use SWAT to administer Samba. Samba is currently installed and working almost successfully however SWAT would make life a bit easier.
I have tried rpm -ivh samba-swat but it can't find the file. ... (1 Reply)
Discussion started by: drag0n
1 Replies
9. Red Hat
Hi,
I have been trying to install SWAT on redhat 6 for samba4. The samba server was installed by another administrator but not swat. Please find output of yum install samba-swat in the attached file (2 Replies)
Discussion started by: p2bas
2 Replies
LEARN ABOUT OPENDARWIN
kill
KILL(1) BSD General Commands Manual KILL(1)
NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page.
SEE ALSO
builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2)
STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD
April 28, 1995 BSD