conf/96160: apache22 is startet before named

Matthias Meyser Meyser at
Sat Apr 22 13:40:16 UTC 2006

>Number:         96160
>Category:       conf
>Synopsis:       apache22 is startet before named
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr 22 13:40:14 GMT 2006
>Originator:     Matthias Meyser
>Release:        FreeBSD 6.0-STABLE i386
XeNET GmbH, Clausthal
System: FreeBSD intserv0.intern 6.0-STABLE FreeBSD 6.0-STABLE #2: Wed Dec 28 14:48:49 UTC 2005 root at intserv0.intern:/usr/obj/usr/src/sys/INTSERV0 i386


	Now we start /usr/local/etc/rc.d scripts in the same order of base
	system rc.d scripts, "apache22" is started BEFORE "named".
	On systems that use a local named for resolving this breaks
	apache22 startup.  ("Can`t resolve....")


	Install an configure apache22.
	Configure named.
	Set resolv.conf to use local named.
        Apache is not started because it could not resolv ist own hostname.


	one fix would be to change "REQUIRE: SERVERS" to "REQUIRE: DAEMON"
	in /usr/local/etc/rc.d/

	I bet this affects all other versions of apache too
	and nearly every networking port. For e.g. samba3 port
	has the same problem.

	So perhaps it is more advisable to assure the named ist started earlier.

More information about the freebsd-bugs mailing list