ports/57031: upslog started with incorrect command line in nut-1.4.0 port

[Don Lewis]

>Number:         57031
>Category:       ports
>Synopsis:       upslog started with incorrect command line in nut-1.4.0 port
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 19 23:50:11 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Don Lewis
>Release:        FreeBSD 4.9-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD mousie.catspoiler.org 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #8: Thu Sep 18 21:02:11 PDT 2003 dl at mousie.catspoiler.org:/usr/obj/usr/src/sys/GENERICDDB i386


	
>Description:
	The command line arguments to upslog in nut.sh.sample are
	incorrect.  As of nut version 1.4.0, it appears that the upslog
	requires the ups name to be specified as well as the host name.
	If the ups name is not specified, upslog just logs 'NA' instead
	of the actual ups statistics.

	The upslog man page also doesn't indicate that
		upslog upsname logfile loginterval
	is the proper syntax.  The example in the man page indicates
	that the ups should be preceeded by the '-s' flag, the log
	file by the '-l' flag, and the log inteval by the '-i' flag.

>How-To-Repeat:
	
>Fix:

	Change the upslog command line in nut.sh.sample to:

	  ${BIN}/upslog -s myups at localhost -l ${UPSLOG} -i ${UPSLOGINTERVAL}


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