search for: suspisi

...ast Message from nut at rasp (somewhere) at 17:33 ... UPS BNT500AP at localhost on line power There were 3 more "on battery" events at 2:31: 43194.030619 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 Here I also see a suspisious frequency value 70. How is this possible? 43194.046966 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x1e, Offset: 0, Size: 8, Value: 70 At 2:58: 44790.984549 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 Here all voltages and fr...

...PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 If you turn up the debugging level from 2 to 3, the driver will do a hex dump of the report buffer. Offset and size are bits, so if the ACPresent bit is 0, that's what the driver reports. > Here I also see a suspisious frequency value 70. How is this possible? > 43194.046966 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x1e, Offset: 0, Size: 8, Value: 70 Similar situation to ACPresent - if those are the bits coming in, that's what the driver reports. Granted, there are cases where usbhid-ups mig...

...ith an 's'. > Using 'vi -b' on log file shows name ending with '^['. Generally when you see something like '^[' that means the control character you get when you hold down the control key and hit '['. Now '^[' is the escape key. That sounds very suspisious. Someone might accidentally get that into a file if they were used to using vi and were editing with a different editor. Perhaps use 'vi -b' on the config file and look everywhere for a '^['. Did the version of Samba you are using come with the operating system or did you build...

...PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 If you turn up the debugging level from 2 to 3, the driver will do a hex dump of the report buffer. Offset and size are bits, so if the ACPresent bit is 0, that's what the driver reports. > Here I also see a suspisious frequency value 70. How is this possible? > 43194.046966 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x1e, Offset: 0, Size: 8, Value: 70 Similar situation to ACPresent - if those are the bits coming in, that's what the driver reports. Granted, there are cases where usbhid-ups mig...

On Jun 8, 2013, at 12:57 PM, M?rti?? Pu??tis wrote: > I'll take a longer driver log. This page (http://www.networkupstools.org/support.html) says that to take a driver log NUT should be stopped, so I won't be able to tell when these events occurred within a driver log. Hmm, I didn't realize it said that, but I think that's to prevent having two copies of the same driver

Thanks for the support. Here's list of when transition to battery with return to utility power within a few seconds occurred in last few days: Wednesday 1:41 11:48 11:54 12:59 13:42 14:42 18:13 18:14 Thursday 5:23 Friday 5:12 7:39 7:43 Saturday 7:34 Here's list of when messages that battery needs replacement occurred: Wednesday 20:34 Thursday 9:07 23:09 Friday 18:25 Saturday 7:32 19:47

In particular, if you want to add support, the right way to know what to rename is (off the top of my head) add a flag or something to have renamepass reset all uses it sees (you only have to change the uses, defs are all linked together and thus already fixed by the updater). Right now it only does that if they have no defining access. Make it skip blocks already in the visited set (the