Date: 07 Nov 2004 20:56:58 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Gary Kline <kline@magnesium.net> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG> Subject: Re: dhcpd (reprise) Message-ID: <443bzlyufp.fsf@be-well.ilk.org> In-Reply-To: <20041107195036.GC30315@toxic.magnesium.net> References: <20041105233628.GA33632@toxic.magnesium.net> <44hdo16376.fsf@be-well.ilk.org> <20041107195036.GC30315@toxic.magnesium.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Kline <kline@magnesium.net> writes:
> I'll add the -d flag to my rc.conf; are you using the latest
No; *disable* dhcpd from rc.conf, and start it by hand with the -d flag.
> version of the dhcp-server from ISC or something other?
I'm running the ISC dhcp server, as I mentioned in my message, and
it's fairly up-to-date, but I don't think the exact version matters
for you (at least not at this point).
> I looked for a 'debug' flag on the man page and didn't see it.
>From "man dhcpd":
To have dhcpd log to the standard error descriptor, specify the -d
flag. This can be useful for debugging, and also at sites where a com-
plete log of all dhcp activity must be kept but syslogd is not reliable
or otherwise cannot be used. Normally, dhcpd will log all output
using the syslog(3) function with the log facility set to LOG_DAEMON.
> What should I loook for in th logfile? or will it be
> obvious :-)
Again, the approach I'm describing will *not* log into the logfile;
I'm suggesting you get the debug output on a console in real time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443bzlyufp.fsf>