Xref: utzoo comp.unix.wizards:20485 comp.unix.ultrix:2737
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.unix.wizards,comp.unix.ultrix
Subject: Re: How do I use /dev/trace?
Message-ID: <9616@cbmvax.commodore.com>
Date: 7 Feb 90 09:19:21 GMT
References: <1148@aoa.UUCP>
Reply-To: grr@cbmvax.cbm.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 22

In article <1148@aoa.UUCP> mbr@aoa (Mark Rosenthal) writes:
> We have been running Ultrix 3.0 on our 8650 for close to a year.  Three times
> in the past two weeks, we have found permissions on /tmp changed.  Naturally,
> when that happens, half the programs in the known universe stop functioning.

I had a similar problem here, and it turned out to be mostly confusion.

What happened was that for some reason I was doing a newfs for the /tmp parition
and then mounting it.  The protection for /tmp directory that I was mounting the
partition on was 777, but when newfs creates a file system, it apparently makes
the "root" entry on the new filesystem have 755'is protection and when you mount
the new filesystem, this is what you get.

Anyway beyond trying to remember to do a newfs/mount/chmod when preparing a new
/tmp or /usr/tmp filesystem, I also stuck a chmod 777 /tmp /usr/tmp after the
mount -a in /etc/rc to protect against future failing.

Please post anything you find out out the sys_trace stuff.  I'm curious.
-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)