Subject: Re: Problem with NetBSD nfs server or SunOS client ?
To: Valtteri Vuorikoski <vuori@sci.fi>
From: Frank van der Linden <frank@fwi.uva.nl>
List: current-users
Date: 03/31/1996 17:25:48
Quoting Valtteri Vuorikoski,

>  There appears to be a problem with either the NetBSD nfs server or the 
> SunOS 4.1.3_u1 nfs client relating to unix domain sockets. The effect is 
> that on the SunOS machine, syslog() doesn't work because it tries to use 
> a unix domain socket in an nfs mounted directory. This is what happens 
> when it tries to use /dev/log (trace from logger, though the same happens 
> with my test program):

> sendto (1, "<13>Mar 30 16:31:28 vuori: foo\n", 31, 0, 0x68d0, 16) = -1 
> ENOTSOCK (Socket operation on non-socket)

>  However, if I put a socket into /tmp (an mfs filesystem) and try to use 
> it (trace from my test program):

> sendto (3, "<13>Mar 30 15:38:18 vuori: foo\n", 31, 0, 0xeffff8b0, 11) = 31

When I tried to reproduce this by booting SunOS 4.1.1_U1 on my Sun3,
it paniced, so something was obviously wrong there on the SunOS side ;-)

Maybe other people can try this on other OSs, using a NetBSD NFS server?

- Frank