From owner-freebsd-isp Sun Aug 20 20:15:18 2000 Delivered-To: freebsd-isp@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 4EC4D37B423 for ; Sun, 20 Aug 2000 20:15:16 -0700 (PDT) Received: from bsdie.rwsystems.net([209.197.223.2]) (1675 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Sun, 20 Aug 2000 22:12:04 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Sun, 20 Aug 2000 22:12:04 -0500 (CDT) From: James Wyatt To: Pete Fritchman Cc: Mike , freebsd-isp@freebsd.org Subject: Re: ps question In-Reply-To: <20000820205802.B27829@databits.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Even if you drop read access to the script, it's just too easy to figure this out for almost anyone. I will be *amazed* if it doesn't break several things. I thought shutdowns used /bin/ps for some reason. - Jy@ btw: The suggested change to the source sounds like the cleanest thing to do, but I'd compare the UID to your lowest login user UID so system scripts and background daemons work as expected. On Sun, 20 Aug 2000, Pete Fritchman wrote: > # mv /bin/ps /bin/ps. > # cat > /bin/ps > #!/bin/sh > /bin/ps. -x > ^D > # > > You can add tests into the script for arguments or the UID/GID calling it, you > get the idea. Basically you need to write a script wrapper. Of course, the > above average luser who _really_ wants to see processes will figure that out and > find /bin/ps. to use. > > Warning, this may have some unwanted side effects... > > -Pete > > ++ 20/08/00 20:51 -0400 - Mike: > >Quick question, how do I make 'ps' work so no matter how users run it, it > >only shows them their processes, and only root can see what -a would display? > >thanks > >Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message