dhcpcd in current..minor concerns

gravityworks · 06-12-2006, 01:08 PM

Just upgraded to the newest version of dhcpcd in the current branch,and noticed alot of dhcp debug info during bootup that werent there before..also noticed that when i do a socklist, udp 68 is listening now(it wasn't before the upgrade)..was wondering if anyone else was seeing the same things..And if so is this a problem with the new dhcpcd package..something he'll fix..or is this just the way dhcpcd does things now..if it is the new way dhcpcd does things..anyone know how to turn off udp 68?

Any help or input would be greatly appreciated..

Alien Bob · 06-12-2006, 03:39 PM

I run Slackware 10.2 and socklist returns this amongst others:

Code:

udp     68       7060       0   2397    7  dhcpcd

Also, dhcpcd spits out all sorts of debug info to the console as long as the syslogger has started. This also happens with my Slackware 10.2 so perhaps you've been running an even older Slackware up to now?

Eric

gravityworks · 06-12-2006, 05:31 PM

first off thanks for the response Alien Bob..

wierd ..this install of slack that i'm using is sort of in constant upgrade it started as slack 10,upgraded to 10.1,10.2 and now to current..never noticed any of the debug stuff during boot before and udp was never listed in socklist..perhaps this dhcpcd upgrade actually fixed something on my setup that i didn't know was broken

..did notice that after the 10.2 upgrade when i rebooted i got a message that /sbin/dhcpcd was not running and know i don't get that message anymore..guess things just sorted themselves out..

patrickdepingui · 06-21-2006, 06:22 AM

I noticed the same thing since I upgraded to the latest current a few days ago... There was something in the changelog:

Quote:

n/dhcpcd-2.0.6-i486-1.tgz: Upgraded to dhcpcd-2.0.6.
Moved /etc/dhcpc/dhcpcd.exe to /etc/dhcpc/dhcpcd.exe-sample to prevent error messages in the log files. The sources install this as non-executable, and there's little reason that I can see to use it in its default form as it only puts redundant information in the logs. It might be a useful stub for some other purpose though...
Thanks to David Houlden and Luis for reporting the issue.

However, I don't see this relating to the appearance of debug messages during boot.
In /etc/rc.d/rc.inet1.conf debugging is turned off:

Code:

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"