home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!caen!U.Chem.LSA.UMich.EDU!hillig
- From: hillig@U.Chem.LSA.UMich.EDU (Kurt Hillig)
- Subject: X windows shared memory transport
- Message-ID: <7hT=rf#@engin.umich.edu>
- Date: Wed, 16 Dec 92 18:38:21 EST
- Organization: Department of Chemistry, University of Michigan, Ann Arbor
- Nntp-Posting-Host: u.chem.lsa.umich.edu
- Lines: 35
-
- 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.
-
- The man page for Xsgi says in part:
-
- Clients may access shared memory by requesting the display shm:0.
- and
- Shared memory transport should not be used on diskless
- systems or systems that mount /usr/tmp from another machine
- via NFS.
-
- Naturally, I'd like to make sure clients don't do this, but clearly
- something is, since the /usr/tmp/shmtrans0 file keeps popping up.
-
- But, if I do a find / ..... | grep "shm:", I can't find any files
- on the system where the "shm:0" display is requested for any
- applications.
-
- So, who's doing this to me? (There are several new Indigos here, and
- lots of students have been playing with the various demos etc. Could
- this be hard-coded into one of the demo programs?)
-
-
- --
- Kurt Hillig
- Dept. of Chemistry I always tell the khillig@umich.edu
- University of Michigan absolute truth Telephone (313)747-2867
- Ann Arbor, MI 48109-1055 as I see it. hillig@chem.lsa.umich.edu
-