On Sunday 12 January 2020 12:09:04 Gene Heskett wrote:
> On Sunday 12 January 2020 11:14:13 Charles Lepple wrote:
> > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote:
> > >> Instant return, logging this:
> > >
> > > in /tmp/info
> > >
> > >> 0.00 Error: too many non-option arguments. Try
On Sunday 12 January 2020 11:14:13 Charles Lepple wrote:
> On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote:
> >> Instant return, logging this:
> >
> > in /tmp/info
> >
> >> 0.00 Error: too many non-option arguments. Try -h for
> >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4
On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote:
>
>>
>> Instant return, logging this:
> in /tmp/info
>
>> 0.00 Error: too many non-option arguments. Try -h for help.
>> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
>> USB communication driver 0.33
>
> This I assumed was with nu
On Saturday 11 January 2020 18:43:23 Gene Heskett wrote:
> On Saturday 11 January 2020 17:00:19 Charles Lepple wrote:
> > On Jan 11, 2020, at 3:50 PM, Gene Heskett wrote:
> > >> The problem is further downstream. Even after you map HID names
> > >> to NUT names, then you run into the fact that CPS
My upssched-cmd script is not modified and having just the following lines:
case $1 in
upsgone)
logger -t upssched-cmd "The UPS has been gone for
awhile"
;;
*)
logger -t upssched-cmd "Unrecognized command: $
You have a point, but how to check the actual manufacturing date?
Regards,
--
Georgi
On 11.1.2020 at 17:54, Manuel Wolfshant wrote:
On January 11, 2020 3:02:59 PM GMT+02:00, "Georgi D. Sotirov"
wrote:
OK. I'll try it, but it really puzzles me how the battery could have
gone bad for just 15
