search for: upsc_list

Displaying 2 results from an estimated 2 matches for "upsc_list".

Did you mean: sc_list
2007 Mar 12
2
Request for comments/testing: upsc_list branch
I finally got some time to implement a pair of options to upsc for listing all configured UPSes on a given upsd: http://boxster.ghz.cc/projects/nut/changeset?new=branches%2Fupsc_list%2Fclients%2Fupsc.c%40859&old=trunk%2Fclients%2Fupsc.c%40821 http://boxster.ghz.cc/projects/nut/browser/branches/upsc_list/clients/upsc.c?rev=859 I think this should work with the new functions for parsing IPv6 addresses, but I haven't set up any IPv6 hosts yet. I will fix the man page if...
2007 Jan 14
1
upscli_splitname() for upsc_list (was: Re: Default NUT PORT)
...tname() > > and upscli_connect(), and an attendant change in all the existing > > clients. When changing the "port" argument to a string, the API should > > also define whether this is allocated (and must be freed) or not. This reminds me: when I was working on branches/upsc_list, the upscli_splitname() function has this comment: /* split [upsname@]hostname[:port] into separate components */ To me, this implies that "upsname@" is optional, but I think this is left over from an older version of NUT (since you have to specify an upsname for upsc). I was thinking...