06-08-2009
Restarting syslogd on Unix
Hi All,
I can seem to find the syslog daemon in the /etc/init.d/ dir. i have made change to the syslog.conf i need to restart the daemon. am using solaris 10. i have no problem on version 9
Anyone with a template i can use for log review for auditing purposes.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Working out of AIX 4.3.
All logs that were written via application suddenly stopped. executing a tail -f <logfile> was not producing any results.
Tried to refresh the syslogd (daemon). When executing "refresh -s syslogd" system would display
<<0513-036 The request could not be passed to... (2 Replies)
Discussion started by: buRst
2 Replies
2. Cybersecurity
Hi all
My system logger has been down for the past 3 days... I am not able to get it to start from the terminal... /etc/init.d/syslogd start
I am unable to find a log as to why it is failing!!
Please advice where to look!!! I am totally lost here!
Thanks in advance...
KS (5 Replies)
Discussion started by: skotapal
5 Replies
3. UNIX for Advanced & Expert Users
I would like to start up multiple instances of syslog daemon. I am having a little difficulty. Is this at all possible?
I have separate syslog.conf1.... syslog.conf5 files.
I have linked the daemon to separate files syslogd1 ... syslogd5
I have arranged the rcd.2 start/stop scripts for... (9 Replies)
Discussion started by: Gary Dunn
9 Replies
4. UNIX for Advanced & Expert Users
I have a remote syslog server which is recieving messages from many hosts. I would like it to log them in seperate files denoted by hostname . For example all messages for host1 in a directory of the same name. Is there an easy way to do this using syslogd? I have a feeling syslog-ng provides this... (3 Replies)
Discussion started by: silvaman
3 Replies
5. Solaris
Hi friends,
is it possible to ignore special messages with syslogd? we have some errors that are firmware issues an no real faults. we serach for a way to ignore ONLY these messages... OS is solaris 10...
any ideas?
tia,
DN2 (1 Reply)
Discussion started by: DukeNuke2
1 Replies
6. Linux
I'm recieving from time to time such messages:
Message from syslogd@localhost at Sat Jul 8 18:29:58 2006 ...
localhost kernel: Disabling IRQ #17
What could cause such messages? How can I at least disable these messages which are posted on all terminals?
Note:
$ uname -a
Linux... (19 Replies)
Discussion started by: Hitori
19 Replies
7. AIX
Hi Guys,
I am configuring syslogd for Message broker.
I know that we have to add a line user.* /var/log/wmb.log
to the /etc/syslog.conf file.
I want to know what userid does the user in user.* take?
Thanks (1 Reply)
Discussion started by: vandi
1 Replies
8. Solaris
Hi ,
Iam using Solaris8 and as I checked I found syslogd process not running
can please somebody suggest me the way to start it. (2 Replies)
Discussion started by: Laxxi
2 Replies
9. Shell Programming and Scripting
Hi,
I need a script to kill the process Ids for the user ABC.
I prepared the following script after that while logging with user therough script i am not sure how to pass the user name and password.Can ou modify the script and help me out.
#!/bin/bash
for filesize in $(ls -ltr | grep... (4 Replies)
Discussion started by: victory
4 Replies
10. Solaris
Where do I configure where syslogd writes to log files?
I've got open files in an archive directory called errlog.131017 and audlog.131017 and, having run an fuser, it appears that syslogd is writing to these files. (3 Replies)
Discussion started by: psychocandy
3 Replies
LEARN ABOUT OPENDARWIN
warn.conf
warn.conf(4) File Formats warn.conf(4)
NAME
warn.conf - Kerberos warning configuration file
SYNOPSIS
/etc/krb5/warn.conf
DESCRIPTION
The warn.conf file contains configuration information specifying how users will be warned by the ktkt_warnd daemon about ticket expiration
on a Kerberos client. Credential expiration warnings are sent, by means of syslog, to auth.notice. All other warning messages are sent to
daemon.notice.
Each Kerberos client host must have a warn.conf file in order for users on that host to get Kerberos warnings from the client. Entries in
the warn.conf file must have the following format:
principal syslog | terminal | mail time [email_address]
principal Specifies the principal name to be warned. The asterisk (*) wildcard can be used to specify groups of principals.
syslog Sends the warnings to the system's syslog. Depending on the /etc/syslog.conf file, syslog entries are written to the
/var/adm/messages file and/or displayed on the terminal.
terminal Sends the warnings to display on the terminal.
mail Sends the warnings as email to the address specified by email_address.
time Specifies how much time before the TGT expires when a warning should be sent. The default time value is seconds, but you
can specify h (hours) and m (minutes) after the number to specify other time values.
email_address Specifies the email address at which to send the warnings. This field must be specified only with the mail field.
EXAMPLES
Example 1: Specifying warnings
The following warn.conf entry
* syslog 5m
specifies that warnings will be sent to the syslog five minutes before the expiration of the TGT for all principals. The form of the mes-
sage is:
jdb@ACME.COM: your kerberos credentials expire in 5 minutes
FILES
/usr/lib/krb5/ktkt_warnd Kerberos warning daemon
SEE ALSO
ktkt_warnd(1M), syslog.conf(4), SEAM(5)
SunOS 5.10 22 Apr 2003 warn.conf(4)