Date: Tue, 23 Nov 1999 21:46:24 -0800 From: Mike Smith <mike@smith.net.au> To: Dan Nelson <dnelson@emsphone.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps on 4.0-current Message-ID: <199911240546.VAA00843@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 23 Nov 1999 18:37:34 CST." <19991123183733.A21142@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> In the last episode (Nov 23), Lyndon Nerenberg said: > > After you verify that this change isn't going to break things that > > assume they can see the *argv list via ps(1). I.e. lightning bolts > > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant > > style, but sometimes is the only workable solution. > > That won't be affected, because anyone that has kill rights to the > process will also see the full processname. Now that I think about it, > I can't come up with a case where this is really bad. If you're doing > ps'es with intent to kill arbitrary processes (in the name of debugging > or whatever), you're probably already root. This was discussed close to death before the changes were committed, and the current behaviour (restricted access) has been agreed by general consensus to be the most appropriate. Making this behaviour tunable would be bad; it adds another option increasing complexity, and with the proposed default in most cases an admin tightening up a system would never know about it in the first place, rendering it useless. I'd strongly recommend leaving things they way they are. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911240546.VAA00843>