<?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: syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945936#M114716</link>
    <description>I periodically clean up syslog using the SAM utility for this.&lt;BR /&gt;&lt;BR /&gt;But till I get around to doing this...I recommend just writing a quick script to clean out any verbose and just informational type statements. And/or maybe a script that looks for important/critical things and sends you a page (or email) for the message...then puts the message in a special file and removes it from syslog.  So far these have worked for me to keep syslog from growing too fast.&lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
    <pubDate>Tue, 08 Apr 2003 10:47:19 GMT</pubDate>
    <dc:creator>Rita C Workman</dc:creator>
    <dc:date>2003-04-08T10:47:19Z</dc:date>
    <item>
      <title>syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945934#M114714</link>
      <description>How can I limit the size of syslog.log in /var/adm/syslog/&lt;BR /&gt;&lt;BR /&gt;Please Help</description>
      <pubDate>Tue, 08 Apr 2003 09:53:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945934#M114714</guid>
      <dc:creator>Daniel Fourie</dc:creator>
      <dc:date>2003-04-08T09:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945935#M114715</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Purge and compress it on a daily basis&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/syslogd stop&lt;BR /&gt;&lt;BR /&gt;mv /var/adm/syslog/syslog.log /var/adm/syslog/syslog.`date`&lt;BR /&gt;&lt;BR /&gt;gzip /var/adm/syslog/syslog.`date`&lt;BR /&gt;&lt;BR /&gt;find /var/adm/syslog ! -newer /var/adm/syslog/syslog.`date` -exec rm {}\;&lt;BR /&gt;&lt;BR /&gt;Then restart which will create a new file&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/syslogd start&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Steve&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Apr 2003 10:08:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945935#M114715</guid>
      <dc:creator>steven Burgess_2</dc:creator>
      <dc:date>2003-04-08T10:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945936#M114716</link>
      <description>I periodically clean up syslog using the SAM utility for this.&lt;BR /&gt;&lt;BR /&gt;But till I get around to doing this...I recommend just writing a quick script to clean out any verbose and just informational type statements. And/or maybe a script that looks for important/critical things and sends you a page (or email) for the message...then puts the message in a special file and removes it from syslog.  So far these have worked for me to keep syslog from growing too fast.&lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Apr 2003 10:47:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945936#M114716</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2003-04-08T10:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945937#M114717</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I prefer putting Steven's script in crontab file, saving only last weeks syslog files</description>
      <pubDate>Tue, 08 Apr 2003 10:58:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945937#M114717</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2003-04-08T10:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945938#M114718</link>
      <description>I like the script.&lt;BR /&gt;&lt;BR /&gt;But, after running gzip won't it have a 'gz' extension?&lt;BR /&gt;&lt;BR /&gt;i.e.&lt;BR /&gt;&lt;BR /&gt;syslog.`date`.gz  ??&lt;BR /&gt;&lt;BR /&gt;Jon</description>
      <pubDate>Wed, 09 Apr 2003 01:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945938#M114718</guid>
      <dc:creator>Jon Finley</dc:creator>
      <dc:date>2003-04-09T01:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945939#M114719</link>
      <description>Once a week the following things happen on my system.&lt;BR /&gt;&lt;BR /&gt;cp /var/adm/syslog/syslog.log /tmp/syslog.log.$DATEVAR&lt;BR /&gt;&lt;BR /&gt;&amp;gt; /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;Zeros the little guy out.&lt;BR /&gt;&lt;BR /&gt;Keeps a copy. DATEVAR has yyyymmdd in it.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 09 Apr 2003 01:50:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945939#M114719</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-04-09T01:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945940#M114720</link>
      <description>I keep several week of syslog.&lt;BR /&gt;Like Steve P using a cron job&lt;BR /&gt;&lt;BR /&gt;I copy the sys log file&lt;BR /&gt; &lt;BR /&gt;and then Compress the Copy&lt;BR /&gt;to save space&lt;BR /&gt;&lt;BR /&gt;echo "" &amp;gt; /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;zero out the file keep you from haveing to stop and start&lt;BR /&gt;cron.&lt;BR /&gt;&lt;BR /&gt;If you don't care about lots of history.&lt;BR /&gt;I would use via cron.&lt;BR /&gt;/sbin/init.d/syslog stop;&lt;BR /&gt;/sbin/init.d/syslog start;&lt;BR /&gt; This process would give you a OLDsyslog.log as if you rebooted.&lt;BR /&gt;&lt;BR /&gt;Rory&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Apr 2003 20:04:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2945940#M114720</guid>
      <dc:creator>Rory R Hammond</dc:creator>
      <dc:date>2003-04-09T20:04:34Z</dc:date>
    </item>
  </channel>
</rss>

