Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BD84E0F.C78160A@cern.ch>
Date: Thu, 25 Oct 2001 19:38:23 +0200
From: "Lassi A. Tuura" <lassi DOT tuura AT cern DOT ch>
Organization: Northeastern University, Boston, USA
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How to debug inetd/sshd services?
References: <3BCEAD9C DOT B2A273B1 AT cern DOT ch> <3BCF1A01 DOT 34CB395F AT cportcorp DOT com> <3BD847F3 DOT 106B0C9E AT cern DOT ch> <3BD84970 DOT 8080502 AT cportcorp DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Did you try sshd -d -d -d? Or is it -v -v -v?

Nothing useful in there :-(

> Search the mail archives for posts about the SYSTEM account,
> especially from Corinna Vinschen. She details the specific
> limitations of the SYSTEM account running a service like sshd
> or inetd. Where it works from the command line, but not as a
> service, it sounds like the SYSTEM account could be involved in
> your problem.

I have read everything I could find, but haven't yet seen anything that
looked like the problem I have.  It might have been explained in some
other context, but then I have missed the connection.  FWIW, I have a
domain account and authenticate using a password.  Based on the most
recent discussion it sounded like this should give sshd enough
information to authenticate fully.  Or did I misunderstand?

Maybe if I try a simple question first: why would cygwin not set
cygdrive prefix according to the value under the HKLM tree?  I deleted
the mounts registry entry in HKCU section, so HKLM should now be the
only setting that could possibly have an effect.  Under what
circumstances this would be expected?

//lat
-- 
But in our enthusiasm, we could not resist a radical overhaul
of the system, in which all of its major weaknesses have been
exposed, analyzed, and replaced with new weaknesses.
--Bruce Leverett, "Register Allocation in Optimizing Compilers"

--
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/