<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: System log files Information in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702796#M58375</link>
    <description>Josmar-&lt;BR /&gt;&lt;BR /&gt;This might not be the best answer, but given the large number of logs, the most complete way would probably be to run a find command to look for everything with a .log extension (or look in SAM or just poke around) and manually open up the logs.  Looking at the last couple pages of the log should give an idea about what it is recording and how often entries get put in.  As to how often to trim or compress, that really depends on how you feel.  Something like a syslog should not be considered the same as something that logs login attempts or something that records IP requests to the web server.  You might be able to find info on some of the logs, but it's not likly that you'll find a shortcut for doing this manually, if you really want to be complete.  My advice is to worry about the big ones (syslog, rclog, etc) and use something like SAM to keep everything else at a decent size.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
    <pubDate>Fri, 12 Apr 2002 16:31:55 GMT</pubDate>
    <dc:creator>Mark Vollmers</dc:creator>
    <dc:date>2002-04-12T16:31:55Z</dc:date>
    <item>
      <title>System log files Information</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702794#M58373</link>
      <description>Hi!!!&lt;BR /&gt;&lt;BR /&gt;I need information about System log files, how to know what are they recording and what are his importance.&lt;BR /&gt;&lt;BR /&gt;I want to rotate logs and I need to know which of them I can compress/remove most frequently.&lt;BR /&gt;&lt;BR /&gt;Where can I find it?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Apr 2002 15:50:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702794#M58373</guid>
      <dc:creator>Josmar Martin</dc:creator>
      <dc:date>2002-04-12T15:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: System log files Information</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702795#M58374</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The system has a lot of log files depends on the applications/process. One important log file is the syslog.log ( /var/adm/syslog). This is the main system log file. For configuring, you can use the /etc/syslog.conf file and the syslogd daemon&lt;BR /&gt;&lt;BR /&gt;# man syslogd&lt;BR /&gt;&lt;BR /&gt;Also there are lot of other log files in the systems - stm logs (/var/stm/logs), /etc/shutdownlog, /etc/rc.log etc. Check the /var directory for log files&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Shiju</description>
      <pubDate>Fri, 12 Apr 2002 16:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702795#M58374</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-04-12T16:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: System log files Information</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702796#M58375</link>
      <description>Josmar-&lt;BR /&gt;&lt;BR /&gt;This might not be the best answer, but given the large number of logs, the most complete way would probably be to run a find command to look for everything with a .log extension (or look in SAM or just poke around) and manually open up the logs.  Looking at the last couple pages of the log should give an idea about what it is recording and how often entries get put in.  As to how often to trim or compress, that really depends on how you feel.  Something like a syslog should not be considered the same as something that logs login attempts or something that records IP requests to the web server.  You might be able to find info on some of the logs, but it's not likly that you'll find a shortcut for doing this manually, if you really want to be complete.  My advice is to worry about the big ones (syslog, rclog, etc) and use something like SAM to keep everything else at a decent size.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Fri, 12 Apr 2002 16:31:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702796#M58375</guid>
      <dc:creator>Mark Vollmers</dc:creator>
      <dc:date>2002-04-12T16:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: System log files Information</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702797#M58376</link>
      <description>In my opinion these would the the log files that you should be concerned with when it comes to its growth. &lt;BR /&gt;Meaning these would be the ones that you would rotate. A good practice would be archived saved logs and only delete them after some time. It depends on the policy you've established at your site. In my case old log files will be deleted after 6 months. &lt;BR /&gt;This is just based on what I have on our system, certainly not exhaustive.&lt;BR /&gt;1- /var/adm/syslog/syslog&lt;BR /&gt;==&amp;gt; The "mother" of all system log files, it logs everything, bootup, hardware errors, connection, etc, etc.&lt;BR /&gt;2- /var/adm/syslog/mail.log&lt;BR /&gt;==&amp;gt; records all sendmail activities&lt;BR /&gt;3- /var/adm/cron/cron.log&lt;BR /&gt;==&amp;gt; Logs cron activation&lt;BR /&gt;4- /var/adm/sw/*.log&lt;BR /&gt;==&amp;gt; SD logs. The one that's going to grow the fastest is swagent.log&lt;BR /&gt;5- /var/adm/lp/log&lt;BR /&gt;==&amp;gt; Logs print spooler activities. Usually quite manageble unless you got a lot of print request.&lt;BR /&gt;6- /var/adm/utmp , wtmp , btmp&lt;BR /&gt;==&amp;gt; Holds info for commands like last, who, write and login.&lt;BR /&gt;7- /var/adm/sulog&lt;BR /&gt;==&amp;gt; Keep tracks of who did su.&lt;BR /&gt;8- /var/adm/shutdownlog&lt;BR /&gt;==&amp;gt; Keep tracks of who did a shutdown/reboot.&lt;BR /&gt;9- /var/sam/log/samlog&lt;BR /&gt;==&amp;gt; Logs SAM related activities.&lt;BR /&gt;10- /var/opt/&lt;VARIOUS-APPLICATIONS-DIR&gt;&lt;BR /&gt;==&amp;gt; At this level, it depends on what application you have on your system. Some examples includes ..perf, OV, samba, ignite..&lt;BR /&gt;&lt;BR /&gt;hope that helps ..&lt;BR /&gt;&lt;/VARIOUS-APPLICATIONS-DIR&gt;</description>
      <pubDate>Sat, 13 Apr 2002 03:07:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-log-files-information/m-p/2702797#M58376</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-04-13T03:07:17Z</dc:date>
    </item>
  </channel>
</rss>

