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: Thu, 1 Feb 2001 00:28:30 +0100 From: Corinna Vinschen To: cygwin Subject: Re: ACCESS_VIOLATION when attempting to run sshd Message-ID: <20010201002830.C15919@cygbert.vinschen.de> Mail-Followup-To: cygwin References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jqj@darkwing.uoregon.edu on Wed, Jan 31, 2001 at 12:40:28PM -0800 On Wed, Jan 31, 2001 at 12:40:28PM -0800, JQ Johnson wrote: > Several people have reported that they got an ACCESS_ERROR running any > command via sshd. I installed cygwin 1.1.7 yesterday, and found the same > problem. My environment: NT 4.0 sp5 workstation, cygwin 1.1.7, with > current cygwin software as of this week. > > In more detail, the symptom is that although sshd may run fine from the > command line, when you run it as a service you find that you can connect > to your NT box, but that every command that is run via ssh produces a core > dump and a Dr Watson dialog box. > > I think I've found a solution: it appears, at least on my system, that > the userid running the sshd service must have the "Log on locally" user > right in addition to "act as part of the operating system", "increase > quotas" (is this really needed? I haven't checked), and "replace a > process level token". This is already documented in /usr/doc/Cygwin/openssh-2.3.0p1.README. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple