ports/131812: network ups tools 2.4.0: upssched SEGVs on startup

[Roy Badami]

>Number:         131812
>Category:       ports
>Synopsis:       network ups tools 2.4.0: upssched SEGVs on startup
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 18 10:30:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Roy Badami
>Release:        7.1-RELEASE-p2
>Organization:
>Environment:
FreeBSD scram.cam.harlequin.co.uk 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #3: Fri Feb 13 10:18:43 GMT 2009     root at scram.cam.harlequin.co.uk:/usr/obj/usr/src/sys/SCRAM  i386
>Description:
In nut-2.4.0 installed from the sysutils/nut port, upssched appears to be non-functional (SEGV's when attempting to schedule an event.)
>How-To-Repeat:
Perform the following steps as root

1. Install nut-2.4.0 from ports.

2. Execute the following commands:
mkdir /var/db/nut/upssched
chown uucp:uucp /var/db/nut/upssched

3. If the upssched directory already existed, remove it's contents to avoid permissions or locking problems:
rm /var/db/nut/upssched/*

4. Create the file /usr/local/etc/nut/upssched.conf with the following contents:
======cut here==========
CMDSCRIPT /usr/bin/true
PIPEFN /var/db/nut/upssched/upssched.pipe
LOCKFN /var/db/nut/upssched/upssched.lock
AT ONBATT * START-TIMER mytimer 5
======cut here==========

5. Simulate upsched being called by upsmon by executing the command:
sh -c 'UPSNAME=test NOTIFYTYPE=ONBATT /usr/local/sbin/upssched "UPS on battery"'

6. Observe that upssched hangs for a while trying to start the daemon, and then SEGV's

7. Execute the command
tail /var/log/messages

8. Observe the log messages indicating that repeated attempts to fork the daemon resulted in SEGV.

9. Tidy up after ourselves:
rm /var/db/nut/upssched/*
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: