X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=E2q5fK
	e0Rkoe2TJnrOPYpH4Lgj/Eh1rPcD7AIL52J0aOajtQR5QxFqIr2o6575A0ljhQ2f
	CW+E74A7r2JPeGuMcvCBj0L88Bd5LMs9WoOqIbfyG7nQrGioKN8cDsHsWkfUydla
	Zd6ef5xN4kv6zksZONBIczAsxbsJUYdPtFr5M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=NapvjHESmQdS
	ozmh6P7Z0axShLI=; b=j42GGWOqwzzDUV3BeEnHF2j9q2aJs18s9uuUJlwLBKm+
	ZxPhkYUSu6tgflVcK4lSfdv1pCSi3gyYCkMks0PXaV+B9hgkBl+TgoEcXJnByqND
	lKyRG/CSiC65ChkcU/THT0dNDhBPzwvRGNTBDUwnoIlxFvFtbAvc9LbwtnmAOXA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
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
Date: Fri, 15 Mar 2019 14:06:17 +0100
Message-ID: <b54aa3b16b27cb12479f382d1ff30e88@smtp-cloud9.xs4all.net>
From: Houder <houder@xs4all.nl>
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> <e9e7c00dbd22a379d425097a72aab8a1@smtp-cloud8.xs4all.net> <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
Note-from-DJ: This may be spam

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

