Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Reply-To: From: "JQ Johnson" To: Cc: , , , , Subject: ACCESS_VIOLATION when attempting to run sshd Date: Wed, 31 Jan 2001 12:40:28 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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". I'd be interested in learning whether this change clears up other people's problems as well. JQ Johnson Office: 115F Knight Library Academic Education Coordinator mailto:jqj AT darkwing DOT uoregon DOT edu 1299 University of Oregon phone: 1-541-346-1746; -3485 fax Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple