conf/58680: [PATCH] RCNG: shouldn't ldconfig be started before SERVERS?

[Andrey Beresovsky]

>Number:         58680
>Category:       conf
>Synopsis:       [PATCH] RCNG: shouldn't ldconfig be started before SERVERS?
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 29 05:00:35 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Andrey Beresovsky
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
Rostov State University
>Environment:
System: FreeBSD 5.1-CURRENT #0: Tue Oct 14 00:39:27 MSD 2003 i386


	
>Description:
I'd like to start/stop named (bind9 from ports) using RCNG with following flags:
named_enable="YES"
named_program="/usr/local/sbin/named"

When I use it manualy (/etc/rc.d/named start|stop|status) it works ok. But 
during system startup it fails because named binary depends on 
/usr/local/lib/libcrypto.so (openssl installed from ports) and rtld can't find
it since ldconfig wasn't ran yet.

I suggest running ldconfig before SERVERS (currently it is being ran before DAEMON)

If this is not "the right thing" then we should find appropriate solution for this problem.

>How-To-Repeat:
1. Build world with NO_OPENSSL and NO_BIND.
2. Install dns/bind9 and security/openssl from ports.
3. Write the following to /etc/rc.conf:
named_enable="YES"
named_program="/usr/local/sbin/named"
4. Reboot.

>Fix:
--- ldconfig    Mon Oct 13 23:35:02 2003
+++ ldconfig.patched    Wed Oct 29 15:41:20 2003
@@ -6,7 +6,7 @@

 # PROVIDE: ldconfig
 # REQUIRE: mountall mountcritremote
-# BEFORE:  DAEMON
+# BEFORE:  SERVERS
 # KEYWORD: FreeBSD NetBSD

 . /etc/rc.subr
>Release-Note:
>Audit-Trail:
>Unformatted: