<?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 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685205#M53935</link>
    <description>Usually if you see this error, rpc.ttdbserver consumes large amount of CPU. Is that your case ? You can do 2 things :-&lt;BR /&gt;&lt;BR /&gt;1)Disable it if you are not using CDE, or if you are not exchanging ToolTalk data between other CDE systems.&lt;BR /&gt;&lt;BR /&gt;2)Or clean up the TTDB database (maybe the DBes are corrupted).&lt;BR /&gt;&lt;BR /&gt;For 1:-&lt;BR /&gt;Kill the process. Comment out the entry from /etc/inetd.conf and re-read the file by running.&lt;BR /&gt;# inetd -c&lt;BR /&gt;&lt;BR /&gt;For 2:-&lt;BR /&gt;Remove all files under each TT_DB subdirectory found under each local file system mount point. Stop rpc.ttdbserver first and restart it after you're done.&lt;BR /&gt;</description>
    <pubDate>Mon, 18 Mar 2002 15:27:32 GMT</pubDate>
    <dc:creator>S.K. Chan</dc:creator>
    <dc:date>2002-03-18T15:27:32Z</dc:date>
    <item>
      <title>syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685204#M53934</link>
      <description>I have this message in syslog.log:&lt;BR /&gt;&lt;BR /&gt;Mar 15 07:57:02 procyon /usr/dt/bin/rpc.ttdbserver[4553]: NetISAM: _iskey_fillmin&lt;BR /&gt;Mar 15 07:57:02 procyon NetISAM[4553]: Fatal error: _iskey_fillmin - UNIX errno 0&lt;BR /&gt;Mar 15 07:57:02 procyon inetd[664]: rpc.ttdbserver/tcp: Exit status 1&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Mon, 18 Mar 2002 15:13:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685204#M53934</guid>
      <dc:creator>Francois Bariselle_3</dc:creator>
      <dc:date>2002-03-18T15:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685205#M53935</link>
      <description>Usually if you see this error, rpc.ttdbserver consumes large amount of CPU. Is that your case ? You can do 2 things :-&lt;BR /&gt;&lt;BR /&gt;1)Disable it if you are not using CDE, or if you are not exchanging ToolTalk data between other CDE systems.&lt;BR /&gt;&lt;BR /&gt;2)Or clean up the TTDB database (maybe the DBes are corrupted).&lt;BR /&gt;&lt;BR /&gt;For 1:-&lt;BR /&gt;Kill the process. Comment out the entry from /etc/inetd.conf and re-read the file by running.&lt;BR /&gt;# inetd -c&lt;BR /&gt;&lt;BR /&gt;For 2:-&lt;BR /&gt;Remove all files under each TT_DB subdirectory found under each local file system mount point. Stop rpc.ttdbserver first and restart it after you're done.&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Mar 2002 15:27:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685205#M53935</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-03-18T15:27:32Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685206#M53936</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check this thread too:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=3c5cbe7c1beb8d17d4/screen=ckiDisplayDocument?docId=200000056575247" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=3c5cbe7c1beb8d17d4/screen=ckiDisplayDocument?docId=200000056575247&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Shiju&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Mar 2002 15:28:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2685206#M53936</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-03-18T15:28:41Z</dc:date>
    </item>
  </channel>
</rss>

