<?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: Configure Syslog.conf in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082027#M142885</link>
    <description>The file that controls logging of error messages via syslog is syslog.conf and man syslogd explains the format of the file. The problem is trying to determine how the message was sent to syslog. There are several 'facilities' and levels of importance. Essentially, each message is processed based on it's facility and importance through the syslog.conf file. So if the error message was generated using a daemon facility and warning level, any of the rules that match thise 2 conditions will be logged to the destination on the right side of the syslog.conf file.&lt;BR /&gt; &lt;BR /&gt;So there is no way to easily associate a particular message (ie, LAN errors, disk errors, etc) with a given facility or even an importance level. If the LAN messages only shows up in syslog and not the console, the default setting in syslog.conf is *.alert which means any facility with alert of higher messages will go to the console. If the LAN messages don't go to the console that would imply that the logging on the console is occurring at at a lower level than alert (which is the second highest). The list is (sorted highest to lowest):&lt;BR /&gt; &lt;BR /&gt;crit&lt;BR /&gt;alert&lt;BR /&gt;err&lt;BR /&gt;warning&lt;BR /&gt;notice&lt;BR /&gt;info&lt;BR /&gt;debug&lt;BR /&gt; &lt;BR /&gt;So if you chenge the line in syslog.conf that contains /dev/co9nsole from:&lt;BR /&gt; &lt;BR /&gt;*.alert  /dev/console&lt;BR /&gt;to&lt;BR /&gt;*.notice  /dev/console&lt;BR /&gt; &lt;BR /&gt;then most likely the message will now also go to the console. The downside is that many more messages may also go to the console too. You can turn on the logging of facility and level information in syslog by changing /etc/rc.config.d/syslogd to start syslog with -v as in:&lt;BR /&gt; &lt;BR /&gt;SYSLOGD_OPTS="-v"&lt;BR /&gt; &lt;BR /&gt;and then restart syslogd using the start/stop script:&lt;BR /&gt; &lt;BR /&gt;/sbin/init.d/syslogd stop&lt;BR /&gt;/sbin/init.d/syslogd start&lt;BR /&gt; &lt;BR /&gt;Now you'll have the code for each message logged in syslog.log (see the man page for syslog for the numbers)</description>
    <pubDate>Tue, 30 Sep 2003 23:01:30 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-09-30T23:01:30Z</dc:date>
    <item>
      <title>Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082023#M142881</link>
      <description>Hello my S.O is hp11i&lt;BR /&gt;&lt;BR /&gt;I need configure syslog.conf for log on console if net cable is disconected.&lt;BR /&gt;And information to use (debug, warning, error, information, alert, etc)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;RenÃ</description>
      <pubDate>Tue, 30 Sep 2003 13:15:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082023#M142881</guid>
      <dc:creator>Rene Mendez_4</dc:creator>
      <dc:date>2003-09-30T13:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082024#M142882</link>
      <description>Not quite sure what you are asking, but if a lan link is disconnected/bad then a message will be logged to the console. This is the default behavior.&lt;BR /&gt; &lt;BR /&gt;If this isn't your issue, could you clarify your question further?&lt;BR /&gt; &lt;BR /&gt;HTH</description>
      <pubDate>Tue, 30 Sep 2003 13:36:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082024#M142882</guid>
      <dc:creator>Brian Bergstrand</dc:creator>
      <dc:date>2003-09-30T13:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082025#M142883</link>
      <description>Hi,&lt;BR /&gt; &lt;BR /&gt;Why don't you post the contents of your /etc/syslog.conf file and we'll go from there?&lt;BR /&gt; &lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Sep 2003 14:08:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082025#M142883</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-09-30T14:08:45Z</dc:date>
    </item>
    <item>
      <title>Re: Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082026#M142884</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;The syslog.conf configure the log in the console and the syslog.log.&lt;BR /&gt;&lt;BR /&gt;If cable of net is disconnect, i need  register in syslog.log and console.&lt;BR /&gt;How to configure this ??&lt;BR /&gt;&lt;BR /&gt;/etc/syslog.conf configuration have any selector (information, warinig, error) way configure this.&lt;BR /&gt;&lt;BR /&gt;Regards &lt;BR /&gt;Rene&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Sep 2003 19:28:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082026#M142884</guid>
      <dc:creator>Rene Mendez_4</dc:creator>
      <dc:date>2003-09-30T19:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082027#M142885</link>
      <description>The file that controls logging of error messages via syslog is syslog.conf and man syslogd explains the format of the file. The problem is trying to determine how the message was sent to syslog. There are several 'facilities' and levels of importance. Essentially, each message is processed based on it's facility and importance through the syslog.conf file. So if the error message was generated using a daemon facility and warning level, any of the rules that match thise 2 conditions will be logged to the destination on the right side of the syslog.conf file.&lt;BR /&gt; &lt;BR /&gt;So there is no way to easily associate a particular message (ie, LAN errors, disk errors, etc) with a given facility or even an importance level. If the LAN messages only shows up in syslog and not the console, the default setting in syslog.conf is *.alert which means any facility with alert of higher messages will go to the console. If the LAN messages don't go to the console that would imply that the logging on the console is occurring at at a lower level than alert (which is the second highest). The list is (sorted highest to lowest):&lt;BR /&gt; &lt;BR /&gt;crit&lt;BR /&gt;alert&lt;BR /&gt;err&lt;BR /&gt;warning&lt;BR /&gt;notice&lt;BR /&gt;info&lt;BR /&gt;debug&lt;BR /&gt; &lt;BR /&gt;So if you chenge the line in syslog.conf that contains /dev/co9nsole from:&lt;BR /&gt; &lt;BR /&gt;*.alert  /dev/console&lt;BR /&gt;to&lt;BR /&gt;*.notice  /dev/console&lt;BR /&gt; &lt;BR /&gt;then most likely the message will now also go to the console. The downside is that many more messages may also go to the console too. You can turn on the logging of facility and level information in syslog by changing /etc/rc.config.d/syslogd to start syslog with -v as in:&lt;BR /&gt; &lt;BR /&gt;SYSLOGD_OPTS="-v"&lt;BR /&gt; &lt;BR /&gt;and then restart syslogd using the start/stop script:&lt;BR /&gt; &lt;BR /&gt;/sbin/init.d/syslogd stop&lt;BR /&gt;/sbin/init.d/syslogd start&lt;BR /&gt; &lt;BR /&gt;Now you'll have the code for each message logged in syslog.log (see the man page for syslog for the numbers)</description>
      <pubDate>Tue, 30 Sep 2003 23:01:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082027#M142885</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-09-30T23:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: Configure Syslog.conf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082028#M142886</link>
      <description>Net cable getting disconnected is a alert and if you have &lt;BR /&gt;&lt;BR /&gt;*.alert                 /dev/console&lt;BR /&gt;&lt;BR /&gt;in /etc/syslog.conf &lt;BR /&gt;&lt;BR /&gt;file that should bring the link down messages on the console&lt;BR /&gt;&lt;BR /&gt;Revert</description>
      <pubDate>Wed, 01 Oct 2003 01:23:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-syslog-conf/m-p/3082028#M142886</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2003-10-01T01:23:01Z</dc:date>
    </item>
  </channel>
</rss>

