Date: Sun, 20 Aug 2000 22:12:04 -0500 (CDT) From: James Wyatt <jwyatt@rwsystems.net> To: Pete Fritchman <petef@databits.net> Cc: Mike <mike@mikesweb.com>, freebsd-isp@freebsd.org Subject: Re: ps question Message-ID: <Pine.BSF.4.10.10008202209350.25370-100000@bsdie.rwsystems.net> In-Reply-To: <20000820205802.B27829@databits.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10008202209350.25370-100000>