<?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 not changing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844541#M393671</link>
    <description>Adonia,&lt;BR /&gt;&lt;BR /&gt;If you are sure /etc/syslogd.conf is correct syntax wise, you can restart the syslogd &lt;BR /&gt;&lt;BR /&gt;kill -1 "pid of syslogd"&lt;BR /&gt;&lt;BR /&gt;This will make syslogd to reread the configuration and log the messages into the location specified in the configuration file.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
    <pubDate>Tue, 23 Oct 2001 00:46:51 GMT</pubDate>
    <dc:creator>Sridhar Bhaskarla</dc:creator>
    <dc:date>2001-10-23T00:46:51Z</dc:date>
    <item>
      <title>Syslog.log not changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844539#M393669</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;I've been having alot of messages going to my syslog.log on my development server, and I've tried archiving it to another volume to save space on /var.  However the syslog.log has not had any new entries put into since late last month and I need to ensure that all message are going to this log.  Is there an easy way to restart whatever process/daemon that populates this log ?    &lt;BR /&gt;Thanks in Advance&lt;BR /&gt;Adonia</description>
      <pubDate>Tue, 23 Oct 2001 00:25:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844539#M393669</guid>
      <dc:creator>Indira Aramandla</dc:creator>
      <dc:date>2001-10-23T00:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log not changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844540#M393670</link>
      <description>To stop (if running) and restart the syslog daemon do, while logged in as root:&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/syslogd stop&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/syslogd start</description>
      <pubDate>Tue, 23 Oct 2001 00:39:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844540#M393670</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2001-10-23T00:39:24Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log not changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844541#M393671</link>
      <description>Adonia,&lt;BR /&gt;&lt;BR /&gt;If you are sure /etc/syslogd.conf is correct syntax wise, you can restart the syslogd &lt;BR /&gt;&lt;BR /&gt;kill -1 "pid of syslogd"&lt;BR /&gt;&lt;BR /&gt;This will make syslogd to reread the configuration and log the messages into the location specified in the configuration file.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Tue, 23 Oct 2001 00:46:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844541#M393671</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2001-10-23T00:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog.log not changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844542#M393672</link>
      <description>Owner of this thread Adonia has left as her contract ended as of August 2002.&lt;BR /&gt;&lt;BR /&gt;Closing this thread.&lt;BR /&gt;&lt;BR /&gt;Indira A</description>
      <pubDate>Sun, 29 Aug 2004 22:28:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-not-changing/m-p/4844542#M393672</guid>
      <dc:creator>Indira Aramandla</dc:creator>
      <dc:date>2004-08-29T22:28:00Z</dc:date>
    </item>
  </channel>
</rss>

