<?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: bootpd message in syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769500#M895985</link>
    <description>Hi Pauline&lt;BR /&gt;&lt;BR /&gt;You don't need to be in single user to modify inetd.conf file&lt;BR /&gt;&lt;BR /&gt;Once you have run inetd -c you will see a reference to inetd re reading config file in your syslog&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Steve&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 22 Jul 2002 19:04:15 GMT</pubDate>
    <dc:creator>steven Burgess_2</dc:creator>
    <dc:date>2002-07-22T19:04:15Z</dc:date>
    <item>
      <title>bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769496#M895981</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Recently I receive these following message in my /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;Jul 22 08:15:54 hobbes bootpd[21674]: reading "/etc/bootptab"&lt;BR /&gt;Jul 22 08:15:54 hobbes bootpd[21674]: read 2 entries from "/etc/bootptab"&lt;BR /&gt;Jul 22 08:58:09 hobbes bootpd[21674]: Exiting after 15 minutes of inactivity&lt;BR /&gt;Jul 22 08:58:34 hobbes telnetd[20135]: Error checking child termination status:&lt;BR /&gt;error 4: Interrupted system call&lt;BR /&gt;Jul 22 08:58:44 hobbes bootpd[22348]: bootpd 2.4 #1.17.112.7: Wed Jul 30 01:28:3&lt;BR /&gt;6 GMT 1997&lt;BR /&gt;&lt;BR /&gt;Please advice.&lt;BR /&gt;Thank you very much,&lt;BR /&gt;Pauline</description>
      <pubDate>Mon, 22 Jul 2002 16:45:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769496#M895981</guid>
      <dc:creator>Pauline Tran</dc:creator>
      <dc:date>2002-07-22T16:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769497#M895982</link>
      <description>Looks like you have the bootps service enabled in /etc/inetd.conf and something on your network is trying to boot from it. Do `man bootpd` to learn more about it. If hobbes is not a network boot server, then this service should be disabled. Perhaps calvin is just poking around.</description>
      <pubDate>Mon, 22 Jul 2002 17:30:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769497#M895982</guid>
      <dc:creator>Jordan Bean</dc:creator>
      <dc:date>2002-07-22T17:30:43Z</dc:date>
    </item>
    <item>
      <title>Re: bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769498#M895983</link>
      <description>Are you suppose to run "bootpd" on this machine ? If you're not, just comment out the "bootpd" entry in /etc/inetd.conf and run "inetd -c" to re-read the file. &lt;BR /&gt;On the other hand if you need bootpd, these messages may not indicate any error. They are simply "operational logs" from the bootp daemon that fills up your syslog.log file. If that is the case I suggest you take a look at the system if it is loaded with the latest "bootpd(1M)/DHCP cumulative" patch. For example (on 11.00 PHNE_19241) if you look at the description of the patch, one of the symptoms in the list is "bootpd mesages filling up syslog.log". This may just be the solution to your problem.&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jul 2002 17:38:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769498#M895983</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-07-22T17:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769499#M895984</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Do I need to do it (modify inetd.conf and run inetd -c ) in single user mode and reboot the server (HP-UX 9000, B.10.20, stand alone server)?&lt;BR /&gt;And if I want the network group find out which machine keep poking my server (they did but could not find which machine...), how can I help them?&lt;BR /&gt;&lt;BR /&gt;Thank you very much,&lt;BR /&gt;Pauline</description>
      <pubDate>Mon, 22 Jul 2002 18:58:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769499#M895984</guid>
      <dc:creator>Pauline Tran</dc:creator>
      <dc:date>2002-07-22T18:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769500#M895985</link>
      <description>Hi Pauline&lt;BR /&gt;&lt;BR /&gt;You don't need to be in single user to modify inetd.conf file&lt;BR /&gt;&lt;BR /&gt;Once you have run inetd -c you will see a reference to inetd re reading config file in your syslog&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Steve&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jul 2002 19:04:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769500#M895985</guid>
      <dc:creator>steven Burgess_2</dc:creator>
      <dc:date>2002-07-22T19:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: bootpd message in syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769501#M895986</link>
      <description>Pauline,&lt;BR /&gt;&lt;BR /&gt;You do not have to configure in single user mode.&lt;BR /&gt;&lt;BR /&gt;As for finding a machine which tried to get this service from your server, it must be on the same subnet as your server.  Hope this may help you narrow down the investigation.  It might be an accident.  For example, someone interrupted an autoboot from a box on the same subnet, searched for all bootable devices which also displayed your bootpd server, and happened to choose as a boot device to boot from.&lt;BR /&gt;&lt;BR /&gt;Hai&lt;BR /&gt;&lt;BR /&gt;Hai</description>
      <pubDate>Mon, 22 Jul 2002 19:12:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootpd-message-in-syslog/m-p/2769501#M895986</guid>
      <dc:creator>Hai Nguyen_1</dc:creator>
      <dc:date>2002-07-22T19:12:00Z</dc:date>
    </item>
  </channel>
</rss>

