ports/131093: chrooting isc-dhcpd to aliased /home can cause devfs-related problems

[Bob Johnson]

>Number:         131093
>Category:       ports
>Synopsis:       chrooting isc-dhcpd to aliased /home can cause devfs-related problems
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 28 21:00:10 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Bob Johnson
>Release:        7.0-RELEASE-p6 amd64
>Organization:
University of Florida
>Environment:
FreeBSD bumble.eng.ufl.edu 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #0: Mon Nov 24 10:59:10 UTC 2008     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
IF isc-dhcp30-server-3.0.7_4 is installed 
AND /etc/rc.conf includes the following lines

dhcpd_enable="YES"
dhcpd_flags="-q"
dhcpd_conf="/usr/local/etc/dhcpd.conf"
dhcpd_ifaces="bge0"
dhcpd_chroot_enable="YES"
dhcpd_rootdir="/home/dhcpd"

AND /home is a link to /usr/home (which is not uncommon)

THEN when "/usr/local/etc/rc.d/isc-dhcpd restart" is run, the script will encounter an error with devfs (don't have exact message, but it said it couldn't create "_" directory in /dev).  To then get dhcpd running requires that the user stop dhcpd, umount /usr/home/dhcpd/dev and then start dhcpd. Also, dev/_ seemed to already exist from original invocation of dhcpd.

WORKAROUND is to give actual path to home dir in rc.conf, i.e. 

dhcpd_rootdir="/usr/home/dhcpd"

then everything works as expected. But it would be nice (i.e. less confusing) if the /home alias could be specified in rc.conf.

>How-To-Repeat:
See above.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: