<?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: SG/MC syslogd in pak? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551227#M714952</link>
    <description>syslogd collects messages from the UNIX domain socket /dev/log.un,  the named pipe /dev/log, and from the kernel log device /dev/klog.&lt;BR /&gt;&lt;BR /&gt;theese devices are specific to your box so you cannot share them with MC/SG&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 11 Jul 2001 08:30:22 GMT</pubDate>
    <dc:creator>Rainer von Bongartz</dc:creator>
    <dc:date>2001-07-11T08:30:22Z</dc:date>
    <item>
      <title>SG/MC syslogd in pak?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551226#M714951</link>
      <description>There are two L-class running HA SG/MC. I like to run the syslogd as HA-Solution listening for other hosts writing logs to the pak.&lt;BR /&gt;How can i run the syslogd in MC/SG listening to the clusternodes and the other hosts?&lt;BR /&gt;&lt;BR /&gt;Kai Bergmann, work-center gmbh, bremen, germany</description>
      <pubDate>Wed, 11 Jul 2001 08:13:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551226#M714951</guid>
      <dc:creator>Kai Bergmann</dc:creator>
      <dc:date>2001-07-11T08:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: SG/MC syslogd in pak?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551227#M714952</link>
      <description>syslogd collects messages from the UNIX domain socket /dev/log.un,  the named pipe /dev/log, and from the kernel log device /dev/klog.&lt;BR /&gt;&lt;BR /&gt;theese devices are specific to your box so you cannot share them with MC/SG&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2001 08:30:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551227#M714952</guid>
      <dc:creator>Rainer von Bongartz</dc:creator>
      <dc:date>2001-07-11T08:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: SG/MC syslogd in pak?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551228#M714953</link>
      <description>Thanks, I know the prob about hte socket.&lt;BR /&gt;In comp.os.hpux..? i?ve read before to start the syslogd to listen to another port than 514.&lt;BR /&gt;Maybe from a chroot,or should we try to take the syslog_ng to our hpux11.0 ? Any other suggestion for runnig logs in pak?</description>
      <pubDate>Wed, 11 Jul 2001 12:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551228#M714953</guid>
      <dc:creator>Kai Bergmann</dc:creator>
      <dc:date>2001-07-11T12:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: SG/MC syslogd in pak?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551229#M714954</link>
      <description>Hi, I think you can't do that because the syslogd only works with your machine.</description>
      <pubDate>Sat, 14 Jul 2001 15:48:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551229#M714954</guid>
      <dc:creator>Alex_17</dc:creator>
      <dc:date>2001-07-14T15:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: SG/MC syslogd in pak?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551230#M714955</link>
      <description>Hi Kai:&lt;BR /&gt;&lt;BR /&gt;The 'syslogd' daemon has the capability of forwarding messages to another host.&lt;BR /&gt;&lt;BR /&gt;For instance, as the man pages (1M) for 'syslogd' indicate, the following entries in /etc/syslog.conf :&lt;BR /&gt;&lt;BR /&gt;*.emerg * &lt;BR /&gt;*.emerg @admin &lt;BR /&gt;&lt;BR /&gt;would enable "emerg" messages to be written to all logged-in users' terminals, and forwarded to the host "admin".&lt;BR /&gt;&lt;BR /&gt;I'm note sure for what use you would like to leverage this capability in an MC/ServiceGuard cluster.  The normal configuation does, of course, write package state changes into the syslog; and for debugging problems, the amount of diagnostic logging can be increased (see KB document #UXSGKBAN00000040).&lt;BR /&gt;&lt;BR /&gt;I suppose you could forward all 'daemon' facility traffic to each node's syslog file.  The setup would have to be specified in every node's /etc/syslog.conf for every host (node) by hostname.&lt;BR /&gt;&lt;BR /&gt;Hopefully you find this helpful.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Sat, 14 Jul 2001 17:52:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-mc-syslogd-in-pak/m-p/2551230#M714955</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-07-14T17:52:44Z</dc:date>
    </item>
  </channel>
</rss>

