bin/51767: /etc/rc.d/virecover in wrong order

[Dominic Mitchell]

>Number:         51767
>Category:       bin
>Synopsis:       /etc/rc.d/virecover in wrong order
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 04 15:10:00 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dominic Mitchell
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD ppe.happygiraffe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Sun May 4 13:54:29 BST 2003 root at ppe.happygiraffe.net:/usr/obj/usr/src/sys/PPE i386


>Description:
	I've been running with rcNG for a while, but I've only just
noticed this problem.  When I rebooted last, I got this message:

Recovering vi editor sessions:/usr/libexec/ld-elf.so.1: Shared object "libsasl2.so.2" not found
.

After a little bit of nosing around, I realised that it's because I
have postfix installed as my MTA, linked against the SASL library.  The
thing that came immediately after that error on my boot sequence was:

ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout

The virecover script was trying to send mail, but failing because
postfix couldn't find its libraries yet.

>How-To-Repeat:

* Set up an alternative MTA to the one in the base system.  Ensure that
  it is dynamically linked against something in /usr/local/lib (sasl or
  ldap should do).

* Start editing a file using /usr/bin/vi.

* Kill the vi process from another terminal.

* Reboot the system.

* Watch the errors...

>Fix:

I guess that the virecover script needs to have ldconfig listed as a
depdendency.  I'm not sure whether any other scripts might need this as
well...
>Release-Note:
>Audit-Trail:
>Unformatted: