Sorry for the late summary but SUMMARY'sa on this list ar most important so better later than never. Many thanks to all that responded. This looks like the answer and now I'm comfortable with just living with it or going into /etc/inetd.conf and commenting out the bootp* entries (& kicking inetd). mha -----Original Message----- From: Dan Astoorian [mailto:djast@cs.toronto.edu] Sent: Friday, May 11, 2001 2:09 PM To: Michael Auria Subject: Re: bootp problem On Fri, 11 May 2001 15:41:23 EDT, Michael Auria writes: > Running Solaris 2.5.1 on Ultra 2 and bootpd is complaining big time. Only 1 > entry in bootptab (see below). Any ideas ... It looks like the hosts listed in the log entries are making bootp requests (or, much more likely, DHCP requests) on the network, and bootpd is logging the fact that it doesn't have entries for them. It doesn't look like a problem to me; if the messages bother you, don't run bootpd with debugging enabled (remove the -d option/argument). -- Dan Astoorian People shouldn't think that it's better to have Sysadmin, CSLab loved and lost than never loved at all. It's djast@cs.toronto.edu not, it's better to have loved and won. All www.cs.toronto.edu/~djast/ the other options really suck. --Dan RedicanReceived on Sun Jun 10 18:12:40 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:56 EDT