- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- configuring syslog.conf
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 12:55 AM
03-07-2002 12:55 AM
I'm searching thinks like :
- this error from this process produce this alarm to the syslog process. For example : a scsi reset from the kernel produce a emergency alarm !!
Thank's a lot.
Olivier.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 01:05 AM
03-07-2002 01:05 AM
Re: configuring syslog.conf
# man 1m syslogd
Also for more info ..
# man 3c syslog
After changes/modifications are made, remember to restart syslogd.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 01:05 AM
03-07-2002 01:05 AM
Re: configuring syslog.conf
Have you check manpage syslogd(1M) and syslog(3C)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 01:10 AM
03-07-2002 01:10 AM
Re: configuring syslog.conf
This link might be helpful:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe8d328e43106d6118ff40090279cd0f9,00.html
Regards,
Mateja
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 01:12 AM
03-07-2002 01:12 AM
Re: configuring syslog.conf
# man 1m syslogd
# man 1 logger
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 01:13 AM
03-07-2002 01:13 AM
SolutionTry man syslogd
That should suffice.
This error from this process means you would need to look at all processes.
Messages are identified by facility and level. If special treatment is needed
for a specific message that is already being logged to syslog the facility and level of
the message must be found.
This can be done by running syslogd in
debug mode.
Run syslog in debug mode by killing the running syslogd daemon and starting it
with /usr/sbin/syslogd -d. This will result in a continuous scrolling
display to the terminal syslogd was just started from.
Look at the "pri" field in the output that scrolls to the screen. The first
character is the facility and the second is the level. The file
/usr/include/syslog.h contains the translations for the fields.
Ex
got a message (1, 0x8)
logmsg: pri 47, flags 0, from nitro, msg Apr 10 09:56:55 : LOGIN:
pam_authenticate error
readfds = 0x68 0x3 0x5 0x6
The facility is 4 so it equates to the following
#define LOG_AUTH (4<<3) /* security/authorization messages */
The facility for this message is "auth". The level is 7 which equates to
"debug". This was determined from the following line in syslog.h:
#define LOG_DEBUG 7 /* debug-level messages */
To send the message above to an extra file add the following lines to the syslog.conf file:
auth.debug /var/adm/authrequests.log
auth.debug /var/adm/syslog/syslog.log
Steve Steel