Red Hat Bugzilla – Bug 170771
dhcp noisy on boot
Last modified: 2007-11-30 17:07:21 EST
+++ This bug was initially created as a clone of Bug #146524 +++
dhcpd is very noisy on bootup, this started happening about the time of some
initscript changes a few weeks back.
When started, the daemon prints out:
[root@tornado init.d]# /etc/init.d/dhcpd start
Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.2rc3
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 4 leases to leases file.
Listening on LPF/eth0/00:0d:61:5e:8b:b3/192.168.0.0/24
Sending on LPF/eth0/00:0d:61:5e:8b:b3/192.168.0.0/24
Sending on Socket/fallback/fallback-net
[ OK ]
It should simply print out:
Starting dhcp: [ OK ]
-- Additional comment from email@example.com on 2005-01-29 16:10 EST --
When dhcp is run from rc.sysinit, ie. during the boot process, or from
"service dhcpd start", these messages should not appear on the terminal
- if they do, it is related to the removal of initlog / minilogd in
initscripts - nothing has changed in dhcpd or the /etc/init.d/dhcpd script
that would cause these messages to appear - they used to be logged via
initlog. This is not a dhcp bug.
-- Additional comment from firstname.lastname@example.org on 2005-02-04 17:52 EST --
It's behaving the same way as if dhcpd was run by hand; in my opinion, if those
are critical messages, they should be logged by the daemon itself. If not, they
should be silenced.
-- Additional comment from email@example.com on 2005-02-11 19:47 EST --
This bug is now fixed in dhcp-3.0.2rc3-3, now in FC4/rawhide .
Please test and let me know if it fixes your problem - thanks.
-- Additional comment from firstname.lastname@example.org on 2005-02-13 07:01 EST --
Yep, resolved now, thanks Jason.
fixed with dhcp-3.0.1-40_EL4+
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.