Can't 'dhcpd -d' in background ?
Glenn.Satchell at uniq.com.au
Fri Jul 14 11:20:04 UTC 2006
>Date: Thu, 13 Jul 2006 07:31:41 -0700 (PDT)
>From: Joe Bill <pica1dilly at yahoo.com>
>Subject: Re: Can't 'dhcpd -d' in background ?
>To: dhcp-users at isc.org
>Simon Hobson <dhcp1 at thehobsons.co.uk> wrote:
> >> Joe Bill wrote:
> >> run 'dhcpd' as root, off it goes on it's own, running in the
> >> run 'dhcpd -d', there it runs in the foreground, locking up your
> > I think you've answered your own question (in part).
> > d=debug ? If you use -d then the process needs to have sterr
> > connected - which effectively means it needs to stay connected to the
> > terminal if started from the command line.
> Hello Simon. Thanks for your lightning fast reply!
> '-d' = debug ? needs to have stderr connected to a terminal ?
> Well, but the man page says "dhcpd log to the standard error descriptor",
> not that it needs a terminal connected.
stderr is file descriptor number 2, so in bash or Bourne shell you can use
dhcpd -d 2>/path/to/logfile
If you want it in the background add an &, eg
dhcpd -d 2>/path/to/logfile &
The default for stderris the terminal. Using 2> is the only simple way
to attach something to stderr.
More information about the dhcp-users