<?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.log file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820607#M269965</link>
    <description>We've seen a few instances where if /var/fills up, and you then free up space in /var, syslog.log will not be written to again untill you stop/start the daemon.</description>
    <pubDate>Mon, 10 Jul 2006 12:00:00 GMT</pubDate>
    <dc:creator>S.Rider</dc:creator>
    <dc:date>2006-07-10T12:00:00Z</dc:date>
    <item>
      <title>Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820602#M269960</link>
      <description>Hi, how can i active syslog file , i mean, i do not have nothing registered there ...&lt;BR /&gt;&lt;BR /&gt;/var/adm/syslog/syslog.log&lt;BR /&gt;Thanks ...</description>
      <pubDate>Mon, 10 Jul 2006 10:37:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820602#M269960</guid>
      <dc:creator>Manuales</dc:creator>
      <dc:date>2006-07-10T10:37:10Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820603#M269961</link>
      <description>your syslog daemon must have been not running.&lt;BR /&gt;&lt;BR /&gt;start it up as follows &lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/syslogd start&lt;BR /&gt;&lt;BR /&gt;hope this helps</description>
      <pubDate>Mon, 10 Jul 2006 10:39:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820603#M269961</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2006-07-10T10:39:24Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820604#M269962</link>
      <description>&lt;BR /&gt;If your syslog daemon is running, you will have to stop and restart it.&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;The most common causes of the syslog daemon not logging:&lt;BR /&gt;&lt;BR /&gt;/var fills up.  this will caise the daemon to no longer write to the log - even after /var has space freed up&lt;BR /&gt;&lt;BR /&gt;the syslog.log file was *moved* or *deleted* without first stopping the daemon.&lt;BR /&gt;&lt;BR /&gt;HTH &lt;BR /&gt;Dave</description>
      <pubDate>Mon, 10 Jul 2006 10:46:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820604#M269962</guid>
      <dc:creator>DCE</dc:creator>
      <dc:date>2006-07-10T10:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820605#M269963</link>
      <description>Manuales,&lt;BR /&gt;&lt;BR /&gt;It's also possible, though not likely, that you're using a non-standard name and/or path for syslog.  Have a look at '/etc/syslog.conf'.  Note where '*.info' messages are being sent.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Mon, 10 Jul 2006 10:58:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820605#M269963</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-07-10T10:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820606#M269964</link>
      <description>The other way to start syslogd if it is running alreay is to syslogd restart&lt;BR /&gt;&lt;BR /&gt;I would also recommend you to check the patch level as sometimes it gets killed if system patches are not updated.&lt;BR /&gt;&lt;BR /&gt;You can check the logging by using logger as well.</description>
      <pubDate>Mon, 10 Jul 2006 11:00:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820606#M269964</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-07-10T11:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820607#M269965</link>
      <description>We've seen a few instances where if /var/fills up, and you then free up space in /var, syslog.log will not be written to again untill you stop/start the daemon.</description>
      <pubDate>Mon, 10 Jul 2006 12:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820607#M269965</guid>
      <dc:creator>S.Rider</dc:creator>
      <dc:date>2006-07-10T12:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820608#M269966</link>
      <description>another reason that the syslog.log is not filling is that there is a "syntax-error" in your /etc/syslog.conf. This would not be reported when you start the syslogd only syslog.log won't be filled. &lt;BR /&gt;Check if tabs or used in stead of spaces between the selectors and the files you want them to be written. &lt;BR /&gt;Check if semicolon is used as separator instead of colon.</description>
      <pubDate>Tue, 11 Jul 2006 07:31:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-file/m-p/3820608#M269966</guid>
      <dc:creator>SGUX</dc:creator>
      <dc:date>2006-07-11T07:31:15Z</dc:date>
    </item>
  </channel>
</rss>

