Displaying 2 results from an estimated 2 matches for "path_to_string".
Did you mean:
xpath_to_string
2006 Mar 14
1
newhidups driver process crashed shortly after upsd loads
...it dies shortly after running with a
segmentation fault. Here is a sample of the last bit of output from
"/usr/local/ups/bin/newhidups -u nut -DDD /dev/hiddev0" (nothing about the
process death is in syslog):
=================
Object: UPS.PresentStatus.VoltageNotRegulated = 0
entering path_to_string()
Looking up 00840002
Looking up ff860080
Object: UPS.PresentStatus.ff860080 = 0
entering path_to_string()
Looking up 00840002
Object: UPS.PresentStatus. = 0
entering path_to_string()
Looking up 00840002
Object: UPS.PresentStatus. = 0
entering path_to_string()
Looking up 00840002
Object: UPS.Presen...
2007 Sep 07
2
Bug#439055: hid driver tries to mmap huge area, fails
...un
> nut recently with no problem, and has a reasonable amount of free memory
> and swap. I stopped many daemons, and the problem persisted.
>
> I tried stracing /lib/nut/newhidups:
>
> write(2, "Path: UPS.Battery.ff86001b, Type"..., 59) = 59
> write(2, "entering path_to_string()\n", 26) = 26
> write(2, "Looking up 00840004\n", 20) = 20
> write(2, "Looking up 00840012\n", 20) = 20
> write(2, "Looking up ff860016\n", 20) = 20
> write(2, "entering string_to_path()\n", 26) = 26
> write(2, "parsing UPS\n&q...