On Sat, Mar 29, 2008 at 06:28:38PM +0100, Arjen de Korte wrote:
>
> You may also want to checkout that you didn't do something
> weird to the STATEPATH (the directory where this socket is
> created). After starting up the driver, you should be able
> to see a listening socket being created there.
>
# strings /lib/nut/usbhid-ups
.
.
/var/run/nut
NUT_STATEPATH
NUT_CONFPATH
/etc/nut
.
.
It looks like the socket is supposed to be built in
"/var/run/nut". This directory exists, but when i run
/lib/nut/usbhid-ups (as root) I do not see a socket there. I
did a chmod 777 to be sure perms on the directory were ok.
What is the socket filename?
Does the following strace segment mean any thing.
.
.
socket(PF_FILE, SOCK_STREAM, 0) = 4
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT
(No such file or directory)
close(4) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 4
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT
(No such file or directory)
close(4) = 0
.
.
--
john
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
