Subject: Re: Syslog getting fat
It's rare to need bootp. It's a precursor to DHCP; very few devices exist today that would need this at all (though many do still offer it as an option: even the wireless printer I bought in 2010 CAN be configured with bootp!).
If you need to use it, the likely problem is that you have a messed up bootptab and need to correct it. It seems to me that there was something else that could cause this, but it's vague: perhaps that a DHCP request was being misinterpreted by bootp (the protocols are extremely similar and bootp isn't all that bright).
If syslog fills up with messages like:
Feb 22 16:11:02 my_box bootpd: version 2.3.5 Feb 22 16:11:02 my_box inetd: /etc/bootpd: exit 0x1 Feb 22 16:11:03 my_box bootpd: version 2.3.5 Feb 22 16:11:04 my_box inetd: /etc/bootpd: exit 0x1
It's a simple fix: if you aren't using bootp, disable it in /etc/inetd.conf
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic