<?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: recommended syslogd messages in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941753#M930124</link>
    <description>I'd be a little cautious. You may well end up with way more going into your syslog than you intended. This can have a knock on effect, as your syslog could grow at an extremely fast rate.&lt;BR /&gt;&lt;BR /&gt;If you're going to do this, keep an eye on how much disk space you have free (so you don't fill up your lvol and cause other problems) and look closely at your log rotation periods (assuming that you have implemented some form of log rotation that is).</description>
    <pubDate>Wed, 02 Apr 2003 12:39:27 GMT</pubDate>
    <dc:creator>Colin Topliss</dc:creator>
    <dc:date>2003-04-02T12:39:27Z</dc:date>
    <item>
      <title>recommended syslogd messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941750#M930121</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;Im looking into enhancing our syslogd messages.  After reading the man page it looks straightforward, but Im wondering if anyone has any suggestions, Im looking at making the level of logging by syslog higher so that i can receive more event notifications.&lt;BR /&gt;&lt;BR /&gt;any help received appreciated!&lt;BR /&gt;&lt;BR /&gt;cheers,&lt;BR /&gt;&lt;BR /&gt;mark.</description>
      <pubDate>Wed, 02 Apr 2003 11:52:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941750#M930121</guid>
      <dc:creator>Richard Woolley</dc:creator>
      <dc:date>2003-04-02T11:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: recommended syslogd messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941751#M930122</link>
      <description>ps, sorry this was meant to go into administration and NOT databases!</description>
      <pubDate>Wed, 02 Apr 2003 11:53:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941751#M930122</guid>
      <dc:creator>Richard Woolley</dc:creator>
      <dc:date>2003-04-02T11:53:45Z</dc:date>
    </item>
    <item>
      <title>Re: recommended syslogd messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941752#M930123</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;1)man syslogd&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; syslogd(1M)                                                     syslogd(1M)&lt;BR /&gt;&lt;BR /&gt; NAME&lt;BR /&gt;      syslogd - log system messages&lt;BR /&gt;&lt;BR /&gt; SYNOPSIS&lt;BR /&gt;      /usr/sbin/syslogd [-d] [-D] [-f configfile] [-m markinterval]&lt;BR /&gt;&lt;BR /&gt; DESCRIPTION&lt;BR /&gt;      The syslogd command reads and logs messages into a set of files&lt;BR /&gt;      described by the configuration file /etc/syslog.conf.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2)You can log own messages using the logger command&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;                    steve Steel</description>
      <pubDate>Wed, 02 Apr 2003 11:54:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941752#M930123</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2003-04-02T11:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: recommended syslogd messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941753#M930124</link>
      <description>I'd be a little cautious. You may well end up with way more going into your syslog than you intended. This can have a knock on effect, as your syslog could grow at an extremely fast rate.&lt;BR /&gt;&lt;BR /&gt;If you're going to do this, keep an eye on how much disk space you have free (so you don't fill up your lvol and cause other problems) and look closely at your log rotation periods (assuming that you have implemented some form of log rotation that is).</description>
      <pubDate>Wed, 02 Apr 2003 12:39:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941753#M930124</guid>
      <dc:creator>Colin Topliss</dc:creator>
      <dc:date>2003-04-02T12:39:27Z</dc:date>
    </item>
    <item>
      <title>Re: recommended syslogd messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941754#M930125</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;The space advice is well put &lt;BR /&gt;&lt;BR /&gt;cat /etc/syslog.conf&lt;BR /&gt;# @(#) $Revision: 74.1 $&lt;BR /&gt;#&lt;BR /&gt;# syslogd configuration file.&lt;BR /&gt;#&lt;BR /&gt;# See syslogd(1M) for information about the format of this file.&lt;BR /&gt;#&lt;BR /&gt;mail.debug              /var/adm/syslog/mail.log&lt;BR /&gt;*.info;mail.none        /var/adm/syslog/syslog.log&lt;BR /&gt;*.alert                 /dev/console&lt;BR /&gt;*.alert                 root&lt;BR /&gt;*.emerg                 *&lt;BR /&gt;&lt;BR /&gt;You can always use different files by moving the syslog out everyday. reducing it to 0 and backing up the days copy.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;                Steve Steel&lt;BR /&gt;</description>
      <pubDate>Wed, 02 Apr 2003 12:46:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recommended-syslogd-messages/m-p/2941754#M930125</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2003-04-02T12:46:13Z</dc:date>
    </item>
  </channel>
</rss>

