Bug 57031 - upslog started with incorrect command line in sysutils/nut (1.4.0) port
Summary: upslog started with incorrect command line in sysutils/nut (1.4.0) port
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Doug Barton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-20 07:50 UTC by Don Lewis
Modified: 2004-02-08 07:34 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Don Lewis freebsd_committer freebsd_triage 2003-09-20 07:50:11 UTC 
	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.

Fix: 

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

	  ${BIN}/upslog -s myups@localhost -l ${UPSLOG} -i ${UPSLOGINTERVAL}
Comment 1 Kirill Ponomarev freebsd_committer freebsd_triage 2003-09-20 09:08:20 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->dougb

Over to maintainer
Comment 2 Doug Barton freebsd_committer freebsd_triage 2004-02-08 07:25:10 UTC 
State Changed
From-To: open->closed


Committed, thanks!