Xref: utzoo comp.unix.questions:15949 comp.unix.ultrix:1582
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sgi!decwrl!gilroy.pa.dec.com!klee
From: klee@gilroy.pa.dec.com (Ken Lee)
Newsgroups: comp.unix.questions,comp.unix.ultrix
Subject: Re: xload: restricted operation on file system
Keywords: xload error message
Message-ID: <1729@bacchus.dec.com>
Date: 25 Aug 89 20:21:43 GMT
References: <714@larry.sal.wisc.edu>
Sender: news@decwrl.dec.com
Lines: 22

In article <714@larry.sal.wisc.edu>, jwp@larry.sal.wisc.edu (Jeffrey W Percival) writes:
> We have a flock of Ultrix vaxes and workstations, and I
> like to have a few "xload" displays on my workstation
> screen.  I do a "rsh foo xload ..." for each CPU I want to look at.
> Most work fine, but one comes back with "restricted operation
> on file system".
> 
> What causes this message, and how do I fix it?

From the xload man page:

     The xload command requires the ability to open and read
     /dev/kmem. On most systems, this requires the suid bit set
     with root ownership or the sgid bit set and membership in
     the same group as /dev/kmem.

A not especially secure alternative is to make /dev/kmem world readable.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee