- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Single syslog.log vs individual log files such as ...
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
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
тАО06-19-2003 01:34 AM
тАО06-19-2003 01:34 AM
Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
I understand that in hpux individual log files can be setup by redefining their directives in /etc/syslog.conf. For example,
mail.debug /var/adm/syslog/mail.log
*.info;mail.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.alert root
*.emerg *
#
# additional ones
#
*.notice /var/adm/notice
*.warn;*.err;mail.info /var/adm/syslog/syslog.log
*.crit /var/adm/critical
auth.* /var/adm/authlog
kern.* /var/adm/kernlog
kern,mark.debug /dev/console
kern.err @phoenix
*.emerg @phoenix
My question is, if I don't specify those entries under the "additional ones" section, will these event entries all go into /var/adm/syslog/syslog.log instead? or will they not show up in syslog.log at all?
Comments and opinions are all welcome.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2003 01:40 AM
тАО06-19-2003 01:40 AM
Re: Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2003 01:47 AM
тАО06-19-2003 01:47 AM
Re: Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
I think whether u add entries above or below "#additional ones" it doesn't make any difference.
So If you are not specifying those entries above or under "additional ones" , those event entries will not go into /var/adm/syslog/syslog.log at all.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2003 01:56 AM
тАО06-19-2003 01:56 AM
Re: Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
Normally you need to be explicit, eg. the following example redirects ftp messages to an ftp.log, instead of syslog.log;
local5.info;mail.none /var/adm/syslog/ftp.log
mail.debug /var/adm/syslog/mail.log
*.info;mail.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.alert root
*.emerg *
Can you see that normally *.info go to syslog (except mail=none - ie. no mail messages), but ive redefined local5.info (local5=ftp messages) to go to ftp.log instead (again, no mail messages).
As there are no kern or auth entries normally in syslog these would not normally be logged by syslog, but in your example they have been setup to go to a separate log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2003 02:08 AM
тАО06-19-2003 02:08 AM
Re: Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
no use of course.Also remember that in your example auth.notice would go to /var/adm/notice and /var/adm/authlog.Can use .none.
I also think that if nothing goes to /dev/console than dmesg is of no use.
Zeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2003 02:08 AM
тАО06-19-2003 02:08 AM
Re: Single syslog.log vs individual log files such as /var/adm/critical, /var/adm/authlog etc
In fact, your above configuration as it stands will probably result in multiple copies of some messages being written to syslog.log. This is because it appears twice in the file with overlapping priority settings.
If you want mail logging into syslog.log you can combine the two syslog.log entries into a single config line:
*.info; mail.info /var/adm/syslog/syslog.log
Note that when you specify a priority code, it includes all messages at that level _and above_. Therefore the *.info includes the *.warn and *.error configurations in your second syslog.log entry.
Hope this makes sense. See the syslogd man page for more details.
Cheers,
Steve