[Nut-upsuser] Tripp Lite OMNI1000 LCD issues

John Darrah xyllyx at gmail.com
Sun Mar 30 03:19:16 UTC 2008


On Sat, Mar 29, 2008 at 10:50:12PM -0400, Charles Lepple wrote:
> On Sat, Mar 29, 2008 at 10:30 PM, John Darrah <xyllyx at gmail.com> wrote:
> >  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"}
> >  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"}
> >  close(4)                                = 0
> 
> This socket does not have anything to do with NUT sockets.
> 
> It is used by libc to check if nscd (Name Service Cache Daemon) has a
> cached copy of a get*ent() value or a DNS lookup. A little further
> down in the strace, you should see it access a file in /etc, or send a
> DNS query over a UDP socket.

Yes, I figured that out moments after hitting the send button ;-)

The only reference to "/var/run/nut" in the strace is a chdir("/var/run/nut").

Does it create the socket after this this chdir?

What would the strace show upon executing the socket creation?



-- 
john



More information about the Nut-upsuser mailing list