Bug 146524 - dhcp noisy on boot
Summary: dhcp noisy on boot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcp
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 170770 170771
TreeView+ depends on / blocked
 
Reported: 2005-01-29 00:32 UTC by Reuben Farrelly
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: dhcp-3.0.2rc3-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-02-13 12:01:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Reuben Farrelly 2005-01-29 00:32:57 UTC
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  ]
[root@tornado init.d]

It should simply print out:

Starting dhcp:             [ OK ]

Comment 1 Jason Vas Dias 2005-01-29 21:10:47 UTC
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.


Comment 2 Bill Nottingham 2005-02-04 22:52:24 UTC
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.

Comment 3 Jason Vas Dias 2005-02-12 00:47:58 UTC
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.

Comment 4 Reuben Farrelly 2005-02-13 12:01:21 UTC
Yep, resolved now, thanks Jason.


Note You need to log in before you can comment on or make changes to this bug.