home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!stanford.edu!nntp.Stanford.EDU!dhinds
- From: dhinds@leland.Stanford.EDU (David Hinds)
- Subject: Re: X windows shared memory transport
- Message-ID: <1992Dec17.001755.973@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (USENET News System)
- Organization: DSG, Stanford University, CA 94305, USA
- References: <7hT=rf#@engin.umich.edu>
- Date: Thu, 17 Dec 92 00:17:55 GMT
- Lines: 17
-
- In article <7hT=rf#@engin.umich.edu> hillig@U.Chem.LSA.UMich.EDU (Kurt Hillig) writes:
- >I've got several networked SGI systems, with one of them acting as
- >an NFS file server. Among other things, I've set up a half-gig
- >shared /usr/tmp filesystem which the clients all NFS-mount.
- >
- >(All are running Irix 4.0.5)
- >
- >The new machines all seem to want to use the "shared memory transport"
- >in Xsgi, which screws things up, since they all try to share the
- >accidentally common /usr/tmp/shmtrans0 file.
-
- I think the easiest way out would be to put a symbolic link in /usr/tmp
- on the server, to point /usr/tmp/shmtrans0 to /tmp/shmtrans0. On each
- client, if /tmp is local, the link will point to the local version.
-
- - David Hinds
- dhinds@allegro.stanford.edu
-