From owner-freebsd-questions Tue Mar 3 10:50:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02116 for freebsd-questions-outgoing; Tue, 3 Mar 1998 10:50:02 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA02044 for ; Tue, 3 Mar 1998 10:49:11 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id TAA15822; Tue, 3 Mar 1998 19:48:18 +0100 Message-ID: <34FC5071.BE448E22@we.lc.ehu.es> Date: Tue, 03 Mar 1998 19:48:17 +0100 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dep. de Electricidad y Electrónica X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG CC: Doug White Subject: Re: KDE 3.1b compiles on 2.2.5, but it doesn't work References: <34FC13DC.7FDB3CF6@we.lc.ehu.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jose M. Alcaide wrote: > ......... > > Then, I thought that the problem could be related to the creation > of named UNIX sockets in the NFS-mounted filesystem, so I searched > for any socket in the .kde directory built by KDE when started > from the local disk, and I found two sockets at ~/.kde/share/apps/kfm, > named "kfm_0.0" and "kio_0.0". However, these same files are created > as **named pipes** (!?!) when KDE is started from the NFS-mounted > home directory. > > ......... > > In summary, I think that the KDE problem is related to the NFS-mounting > of the user account, but my little program creates sockets in the > remote filesystem, so I don't know what happens. > I think that I have reached the end of my KDE problem that began this thread. The guilty is... the NFS server!!!! We use as our main NFS server for user directories a SPARCserver running Solaris 2.5.1. When an NFS request for creating a socket comes from any NFS client, the server makes it with permissions 750 (this is OK) and the setuid bit set (I don't know why). But after creating the sockets, KDE changes their modes to 666 (BTW, the number of the Beast :-) ); this implies that the client requests a SETATTR NFS operation to the Solaris server. I have found that this simple operation changes the file type from "socket" to "pipe". This only happens in the Solaris server. I have tested also an SGI IRIX NFS server and the mode change works fine from any client. In summary, my KDE problem has only two possible solutions: 1. Sun fixes the Solaris' NFS server code. 2. KDE is changed so that it creates the sockets in a local filesystem (such as /tmp). ARRRRRGH!!!! -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-4-4647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-4-4858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message