Sponsored Content
Full Discussion: syslog hup
Operating Systems Linux syslog hup Post 302217434 by reborg on Tuesday 22nd of July 2008 10:05:19 PM
Old 07-22-2008
That is exactly what you expect when you kill -HUP a daemon, the pid should not change.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hup

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

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

6. Solaris

Which are the available entries to forward syslog in syslog.conf?

Hi Community Which are the available entries to forward syslog in syslog.conf i have put *.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50 and it's not going through.giving error message like below: syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies

7. AIX

Cannot send syslog event from AIX 6.1 to RHEL Syslog server

Hi everyone, I am trying to configure AIX 6.1 using syslogd to send syslog event to syslog server configured on RHEL. However, RHEL never receives the events. I have tried to redirect the syslog event on AIX to a local file and successful. Only forwarding to remote server fails. Firewall... (10 Replies)
Discussion started by: michael_hoang
10 Replies
syslog_evm.conf(4)					     Kernel Interfaces Manual						syslog_evm.conf(4)

NAME
syslog_evm.conf - EVM syslog subscription configuration file SYNOPSIS
facility.priority DESCRIPTION
The syslog_evm.conf file is a text file that specifies what syslog messages will be forwarded from the syslog daemon to the Event Manager, EVM,in the form of EVM events. Those syslog messages are posted to the EVM daemon evmd by syslogd if the syslogd forwarding function is turned on with the -e flag. Events are posted with the EVM name of sys.unix.syslog.facility-name. This configuration file is read every time syslogd starts, or is restarted by a SIGHUP signal. If the file does not exist, or if it exists but contains no subscription lines, no syslog messages will be posted to EVM. Each line in the file controls the forwarding of one syslog event. Lines beginning with the # character are considered comments and are ignored. Only one subscription per line is permitted. Mixing a subscription and a comment on the same line is not allowed. Each line has the format facility.priority[+]. Specifies the part of the system that generated the message. Legal values are the follow- ing: All messages. Messages generated by the kernel. Messages generated by user processes. Messages generated by the mail system. Mes- sages generated by system daemons. Messages generated by the authorization system. Messages generated internal to the syslog system. Messages generated by the line printer spooling system. Messages generated by the system news command. Messages generated by the UNIX to UNIX copy system. Messages generated by the system clock daemon. Messages generated by remote file systems. Available for local use. Indicates the priority of the message. If the priority is followed by a + character, events which are of the specified priority or higher are forwarded; otherwise only events which exactly match the priority are forwarded. The priority level must be one of the following: Forward messages of any priority. Forward messages of emergency priority. Forward messages of alert priority. Forward messages of critical priority. Forward messages of error priority. Forward messages of warn- ing priority. Forward messages of notice priority. Forward messages of information priority. Forward messages of debug priority. EXAMPLES
This example causes syslogd to forward events to EVM as follows: All messages of emergency priority are forwarded. All messages generated in the kernel which have a priority of info or greater are forwarded. All messages generated by users, by the mail subsystem or by the system daemons which have a priority of info or greater are forwarded. *.emerg kern.info+ user.notice+ mail.notice+ daemon.notice+ FILES
Location of the system logger configuration file. Location of the EVM syslog subscription configuration file. Location of the EVM logger configuration file. SEE ALSO
Commands: evmd(8), evmlogger(8), syslog(1), syslogd(8) Routines: syslog(3) Event Management: EVM(5) delim off syslog_evm.conf(4)
All times are GMT -4. The time now is 04:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy