pkg/38055: gated startup rc-file broken - filesystem not mounted at this time

[Wolfgang.Stukenbrock%nagler-company.com@localhost]

>Number:         38055
>Category:       pkg
>Synopsis:       gated startup rc-file broken - filesystem not mounted at this 
>time
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 18 15:45:00 +0000 2008
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 4.0 - pkgsrc-2007Q4
>Organization:
Dr. Nagler & Company GmbH
        
>Environment:
        
        
System: NetBSD s011 4.0 NetBSD 4.0 (NSW-S011) #17: Mon Feb 18 12:51:48 CET 2008 
wgstuken@s012:/export/NetBSD-4.0/N+C-build/.OBJDIR_i386/export/NetBSD-4.0/src/sys/arch/i386/compile/NSW-S011
 i386
Architecture: i386
Machine: i386
>Description:
        In the example startup file (/usr/pkg/share/examples/rc.d/gated) gated 
is started after network and mountcritlocal
        but before NETWORKING.
        A this time /usr and /usr/pkg are not mounted - and gated is installed 
as /usr/pkg/sbin/gated.
        During the boot process, the gated startup is ignored without any error 
indication on the console, due to
        the missing binary in /usr/...
        This leads to a system startup without gated running and the 
administrator searching for the problem ...
        A second problem is, that gated expects syslogd to be up and running.
        But syslogd startup expects, that that network setup has completed - at 
least the netbsd rc-files force this.
>How-To-Repeat:
        install gated from pkgsrc-2007Q4 and try to start it during boot 
process using e.g. the example startup file.
>Fix:
        Not realy known to me.
        For me I've fixed the problem by starting gated after syslogd before 
SERVERS - but this may break other assumtions in
        other setups.

        Perhaps it would be a good idea to install such essential programs on a 
path like /etc/pkg/sbin to have them on the
        root filesystem and start newsyslog and syslogd in front of the routing 
daemons. Syslogd is started prior named in the current
        setup, so syslogd seems to be resistent agains hostname lookup failure 
and should also be resistend agains problems sending
        messages to remote systems.


>Unformatted: