10 More Discussions You Might Find Interesting
1. Solaris
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
2. BSD
I'm trying to get all ipfw logs going to ipfw.log I've managed that, but ipfw.log is also getting stuff that shows up in system.log
!-ipfw
*.notice;authpriv,remoteauth,ftp,install,internal.none /var/log/system.log
kern.* /var/log/kernel.log... (5 Replies)
Discussion started by: jnojr
5 Replies
3. Red Hat
Hi,
I would like to configure syslog linux client, syslog server is windows server.
so adding on linux client in /etc/syslog.conf @hostname will work in the place of directory location.
example of /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up... (2 Replies)
Discussion started by: manoj.solaris
2 Replies
4. Solaris
I would like to configure the syslog.conf to have a good monitoring information about my system.
do you have any idea about best configuration from your experience in your Data Centers
BR, (5 Replies)
Discussion started by: maxim42
5 Replies
5. UNIX for Advanced & Expert Users
I have a RHEL box that I want to be the loghost for all of the other systems on my network and have set up a /logs partitions to hold all of the logs. I've also created a file called current.log that will contain daily logs and created it using the following command: cp /dev/null current.log. ... (4 Replies)
Discussion started by: goose25
4 Replies
6. Solaris
Hi Everyone,
I just wanted to know about the below entry in syslog.conf in Solaris 10:
kern.notice @destserver
Now the log will be redirected to destserver. But I want to know the location on the destserver where this log will be thrown.
Thanks in Advance,
Deepak (4 Replies)
Discussion started by: naw_deepak
4 Replies
7. UNIX for Dummies Questions & Answers
Hi,
We had a hardware problem at work and none of the kernel problems outputted to the log file, just the screen. How can I configure the syslogd.conf file to record kernel events (ie hardware problems) to /dev/console and/var/log/messages. Can I just put:
/dev/console /var/log/messages on... (5 Replies)
Discussion started by: mojoman
5 Replies
8. Solaris
Has anyone here configured a central syslog server using syslog-ng ?
I have set one up and I'm trying to tune the syslog-ng.conf file, both for the server and the client. I have found lots of linux example files, but not much on Solaris which is slightly different.
So if you have a Solaris... (5 Replies)
Discussion started by: Tornado
5 Replies
9. Linux
Hi everybody,
i have a little problem...
I have two server srv01 and srv02.
srv02 have a syslogd server onboard and listen on 515... not on 514 (it's busy).
How i configure the syslog.conf of srv01 for send logs on srv02:515 ???
Now i have on srv01:
*.* @srv02
if i write:
*.* ... (0 Replies)
Discussion started by: Zio Bill
0 Replies
10. Red Hat
Hi all
I have a RedHat Linux AS2.1 server that keep crashing/rebooting and there are no messages in the /var/log/messages file pointing to any problems. I had a look at the /etc/syslog.conf file to see what gets logged to /var/log/messages, but I don't know what else to add. Can anyone tell me... (1 Reply)
Discussion started by: soliberus
1 Replies
drd(1M) System Administration Commands drd(1M)
NAME
drd - Logical Domain Dynamic Reconfiguration daemon
SYNOPSIS
/usr/lib/ldoms/drd
DESCRIPTION
The drd daemon is part of the framework that enables the addition and removal of resources from a Logical Domain. This framework is collec-
tively called Dynamic Reconfiguration (DR).
drd is responsible for various aspects of DR on a Logical Domain and must be enabled to ensure proper DR functionality. It is started at
boot time and has no configuration options.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWldomu |
+-----------------------------+-----------------------------+
|Interface Stability |Unstable |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), svcadm(1M), syslog(3C), syslog.conf(4), attributes(5), smf(5)
ERRORS
drd uses syslog(3C) to report status and error messages. All of the messages are logged with the LOG_DAEMON facility. Error messages are
logged with the LOG_ERR and LOG_NOTICE priorities, and informational messages are logged with the LOG_INFO priority. The default entries in
the /etc/syslog.conf file log all the drd error messages to the /var/adm/messages log.
NOTES
The drd service is managed by the service management facility, smf(5), under the service identifier:
svc:/platform/sun4v/drd:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
SunOS 5.11 10 Jul 2006 drd(1M)
