<?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: messages to syslog.log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608114#M35462</link>
    <description>Do a man on syslogd, and modify /etc/syslog.conf file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
    <pubDate>Tue, 06 Nov 2001 13:48:00 GMT</pubDate>
    <dc:creator>harry d brown jr</dc:creator>
    <dc:date>2001-11-06T13:48:00Z</dc:date>
    <item>
      <title>messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608113#M35461</link>
      <description>Hello.&lt;BR /&gt;&lt;BR /&gt;I??ve a program who send msg??s to /dev/syscon (I don??t know how and I can??t rewrite the program), and I want to catch this msg??s to syslog.log.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Nov 2001 13:31:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608113#M35461</guid>
      <dc:creator>Lukas Grijander</dc:creator>
      <dc:date>2001-11-06T13:31:21Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608114#M35462</link>
      <description>Do a man on syslogd, and modify /etc/syslog.conf file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Tue, 06 Nov 2001 13:48:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608114#M35462</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2001-11-06T13:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608115#M35463</link>
      <description>Harry's right in that syslog.conf is the first place to look.  It is possible though that the program is not using syslogd for routing its messages to /dev/syscon.   The best option would be to find the programmer and make sure they are using syslog utilies for messages.  If that is not possible, you will have to look for an alternative such as putting a wrapper around the program to ensure messages are routed somewhere else.</description>
      <pubDate>Tue, 06 Nov 2001 14:52:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608115#M35463</guid>
      <dc:creator>Bernie Vande Griend</dc:creator>
      <dc:date>2001-11-06T14:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608116#M35464</link>
      <description>Does it do an append? why not link it to the syslog.log?&lt;BR /&gt;ln -s /var/adm/syslog.log whateverlog&lt;BR /&gt;&lt;BR /&gt;James</description>
      <pubDate>Tue, 06 Nov 2001 15:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608116#M35464</guid>
      <dc:creator>James Beamish-White</dc:creator>
      <dc:date>2001-11-06T15:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608117#M35465</link>
      <description>my /etc/syslog.conf has this line :&lt;BR /&gt;&lt;BR /&gt;*.debug /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;so, I understand all msg??s go to syslog.log, but must these msg??s be sent through syslog routines?&lt;BR /&gt;&lt;BR /&gt;echo "HELLO" &amp;gt; /dev/syscon&lt;BR /&gt;&lt;BR /&gt;don??t send the msg to syslog.log&lt;BR /&gt;&lt;BR /&gt;but &lt;BR /&gt;&lt;BR /&gt;logger "HELLO" &lt;BR /&gt;&lt;BR /&gt;send twice the same msg to syslog.log&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Tue, 06 Nov 2001 15:24:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608117#M35465</guid>
      <dc:creator>Lukas Grijander</dc:creator>
      <dc:date>2001-11-06T15:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608118#M35466</link>
      <description>Are you sure it logs to /dev/syscon, not /dev/console?&lt;BR /&gt;&lt;BR /&gt;If it logs to /dev/console or syscon is linked to console, and you have a (CDE/VUE) GUI, you can use a hpterm(1) window with the "-C" option to catch (/dev/console) console messages.&lt;BR /&gt;&lt;BR /&gt;Alternatively you can try to use a binary editor on the executable file to change /dev/syscon to some other, equally 'long' name. A simple binary editor is "vis -n", your favorite *text* editor (vi(1)) and "inv -n".</description>
      <pubDate>Tue, 06 Nov 2001 15:49:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608118#M35466</guid>
      <dc:creator>Frank Slootweg</dc:creator>
      <dc:date>2001-11-06T15:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608119#M35467</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;  /dev/syscon is console,&lt;BR /&gt;as the list on it shows below.&lt;BR /&gt;****************&lt;BR /&gt;crw--w--w-   1 root       sys          0 0x000000 Nov  5 11:07 /dev/console&lt;BR /&gt;crw--w--w-   2 bin        bin          0 0x000000 Jul 31 14:57 /dev/syscon&lt;BR /&gt;*****************&lt;BR /&gt;&lt;BR /&gt;So the messages are going&lt;BR /&gt;to console.  If you want&lt;BR /&gt;them to go to syslog.log file,&lt;BR /&gt;then the change has to be&lt;BR /&gt;made in application to&lt;BR /&gt;redirect the messages to&lt;BR /&gt;syslog file (append) .&lt;BR /&gt;&lt;BR /&gt; Is this a uSer application&lt;BR /&gt;or  a system-related application?&lt;BR /&gt;&lt;BR /&gt;-raj</description>
      <pubDate>Tue, 06 Nov 2001 16:41:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608119#M35467</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2001-11-06T16:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608120#M35468</link>
      <description>First thing i were do is &lt;BR /&gt;strings your_program | grep /dev. See man strings for options.&lt;BR /&gt;&lt;BR /&gt;If you find /dev/syscon or /dev/console use adb to change it to /dev/null or a pipe file you can manage. &lt;BR /&gt;&lt;BR /&gt;JRF seems to be the master of adb, he can help you.</description>
      <pubDate>Tue, 06 Nov 2001 23:45:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608120#M35468</guid>
      <dc:creator>Carlos Fernandez Riera</dc:creator>
      <dc:date>2001-11-06T23:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: messages to syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608121#M35469</link>
      <description>RajMan, /dev/syscon is not exactly the same as [/dev/]console, that is why I wrote "If ... syscon is linked to console".&lt;BR /&gt;&lt;BR /&gt;See your own ll(1) output. The link count for /dev/syscon is 2, while the link count for /dev/console is 1. This means that they are *not* (hard) linked. You can see this by doing a "ll -i" which shows that the inode numbers are different. (Also the different UID/GID/timestamp show that they are not (hard) linked.)&lt;BR /&gt;&lt;BR /&gt;However that they are not (hard) *linked* does not neccessarily mean that they are not *pointing* to the same physical device.&lt;BR /&gt;&lt;BR /&gt;See the init(1M) manual page on how /dev/syscon (the *logical* system console) and /dev/systty (the *physical* system console) interact.&lt;BR /&gt;&lt;BR /&gt;The bottom line in that in *most* cases /dev/console, /dev/syscon and /dev/systty point to the same physical device, but not in *all* cases.</description>
      <pubDate>Wed, 07 Nov 2001 07:51:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/messages-to-syslog-log/m-p/2608121#M35469</guid>
      <dc:creator>Frank Slootweg</dc:creator>
      <dc:date>2001-11-07T07:51:26Z</dc:date>
    </item>
  </channel>
</rss>

