>Number:         26830
>Category:       bin
>Synopsis:       ifwatchd should call carrier up/down scripts at startup
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 02 07:53:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Martin Husemann
>Release:        NetBSD 2.0G
>Organization:
>Environment:
System: NetBSD beasty.aprisoft.de 2.0G NetBSD 2.0G (NIGHT-OWL) #1: Mon Aug 30 22:47:16 CEST 2004 martin@night-owl.duskware.de:/usr/src/sys/arch/i386/compile/NIGHT-OWL i386
Architecture: i386
Machine: i386
>Description:

To make configuration changes via ifwatchd(8) scripts stateless, ifwatchd 
should at startup call the appropriate carrier scripts (just like it does
for up/down scripts).

If you rely on configuration via those scripts, you now have to duplicate 
those somewhere for boot time (i.e. in /etc/rc.local).

>How-To-Repeat:

Connect a network cable to your ethernet interface, then manually start
"ifwatchd ${if} -c myscript" and watch it not execute myscript imediately. 

>Fix:
At startup time, query interface status and call proper carrier script.
(As a side effect, this might work around the symptoms described in
PR kern/26829)
>Release-Note:
>Audit-Trail:
>Unformatted: