HP-UX how to get all of the syslog Post: 302683371

Sponsored Content

Operating Systems HP-UX HP-UX how to get all of the syslog Post 302683371 by methyl on Tuesday 7th of August 2012 08:04:52 PM

08-07-2012

Registered User

The flat file /var/adm/syslog/syslog.log is not suitable for storing every event which can happen on a HP-UX 11.11 system (I assume that is what you mean by 11i) ... or any unix system for that matter.

There are separate detailed but compact databases maintained by the Enviromental Mangement System (EMS) to record all hardware events including the trivia such as correctible memory errors and routine changes of exchangeable media. Any serious hardware errors are also recorded in syslog.log and each message includes the EMS command to get the detail of the error.

I feel that you are presenting us with your non-viable solution to your problem, rather than presenting the problem itself.

I still suggest that you approach HP in your own language with your requirement. They may try to sell you HP Vantagepoint (aka Openview) and some consultancy.

methyl

View Public Profile for methyl

Find all posts by methyl

2 More Discussions You Might Find Interesting

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

LEARN ABOUT SUNOS

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)