Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 18 May 2004 14:40:19 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Problems listing tasks under cygwin. In-Reply-To: <40AA571A.C2ACDB24@dessent.net> Message-ID: References: <40AA571A.C2ACDB24@dessent.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Tue, 18 May 2004, Brian Dessent wrote: > Dave Korn wrote: > > > Actually, SYSTEM has higher privileges in general than root. It may > > well be impossible to kill some tasks belonging to system because they > > may not allow full access even to users with admin rights. The error > > message may be misleading, and maybe it should be saying "Access > > denied". > > FYI, you can kill SYSTEM processes as a regular user administrator > account using Process Explorer from sysinternals.com. I haven't checked > but I believe the program installs a helper driver that runs as SYSTEM > to perform these actions as proxy for the user. A lot of the > sysinternals tools do something like that it seems. > > Brian ...Which means that currently in Cygwin one should be able to kill a SYSTEM-owned task from a SYSTEM-owned shell (using the "at /interactive" trick), and that once "su via cygserver" is operational, one can simply do "su SYSTEM kill PID"... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/