Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 13 Nov 2001 11:41:58 +0000 Message-ID: <6049-Tue13Nov2001114158+0000-starksb@ebi.ac.uk> X-Mailer: emacs 20.7.1 (via feedmail 9-beta-7 I); VM 6.92 under Emacs 20.7.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Corinna Vinschen Subject: Re: How do I figure out why LogonUserA is failing? In-Reply-To: <20011113100434.A18765@cygbert.vinschen.de> References: <200111122339.PAA19144@cygnus.com> <20011113100434.A18765@cygbert.vinschen.de> On Tuesday 13 Nov 01, Corinna Vinschen writes: > LogonUser/CreateProcessAsUser need special user rights. This rights > are not given to user accounts, not even to admins. Only SYSTEM has > that user rights by default. That's the reason that login only > works when started from telnetd or rlogind, started from inetd which > itself is running as service under SYSTEM account. > > login(1) is not intended for use on the command line under Cygwin. > > Shouldn't we create a FAQ for that? There is already something about why there is no su, but it goes on to say (indirectly) that login(1) may be a substitute. I will amend it to include the information you provide above. (I don't know about this stuff myself, so I can't put it in the FAQ until I get concise, pithy emails like this one. Thanks Corinna!) Cheers, David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/