From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50134 invoked by alias); 15 Mar 2019 13:06:23 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 50120 invoked by uid 89); 15 Mar 2019 13:06:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=patients, fire, sticking, HX-Languages-Length:1735 X-HELO: lb2-smtp-cloud9.xs4all.net Received: from lb2-smtp-cloud9.xs4all.net (HELO lb2-smtp-cloud9.xs4all.net) (194.109.24.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Mar 2019 13:06:20 +0000 Received: from tmp.DKea0Q5S1g ([83.162.234.136]) by smtp-cloud9.xs4all.net with ESMTPSA id 4mXOhpKQ3I8AW4mXPhn0Ny; Fri, 15 Mar 2019 14:06:17 +0100 Date: Fri, 15 Mar 2019 13:06:00 -0000 Message-ID: From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: sshd: fatal: seteuid XXX : No such device or address References: <011a01d4da5a$96247330$c26d5990$@giraudbtp.com> <20190314172918.GJ3785@calimero.vinschen.de> In-Reply-to: <20190314172918.GJ3785@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-SW-Source: 2019-03/txt/msg00405.txt.bz2 On Thu, 14 Mar 2019 18:29:18, Corinna Vinschen wrote: > On Mar 14 16:53, Houder wrote: > > On Thu, 14 Mar 2019 12:39:30, XXXXX wrote: > > > Hello the list [snip] > > > sshd: PID 3777: fatal: seteuid 1049076: No such device or address > > Corinna, > > > > As far as I know, seteuid() can either return EINVAL or EPERM in case of > > an error. > > > > EPERM (=3D 1) "Operation not permitted" > > EINVAL(=3D 22) "Invalid argument" > > > > "No such device or address" appears to correspond to ENXIO (=3D 6). Is it > > sshd, or is it Cygwin, that is confused here? > > No confusion as such. The underlying Windows function returns a NT > status code, which is converted to a Win32 error code by a Windows > function, and that Win32 error code is converted to a POSIX errno by > Cygwin. There are much more NT status codes than Win32 error codes, and > there are much more Win32 error codses than POSIX errno values, so the > mapping is inevitably unsatisfying. .. yes, I am aware of the situation (winsup/cygwin/errno.cc) ... However, in the end this kind of error messages is of NOT much use in order to ascertain what is going on (i.e. what is causing the problem). One is forced to create the exact same environment (system) as the person who is complaining, fire up the debugger (like sticking a thermometer in a patient's rear end) in order to find out where the code failed ... Meaning, within the context of the recent sshd problems, possibly only you know where the error ERROR_FILE_INVALID (resulting in the error message "No such device or address") was generated ... (and by which Windows function). Oh well, this cannot be helped ... Thank you. Regards, Henri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple