X-Spam-Check-By: sourceware.org
Message-ID: <31b7d2790706220859g4b6ec2a5k6cdb70fdba7441dc@mail.gmail.com>
Date: Fri, 22 Jun 2007 10:59:51 -0500
From: "DePriest, Jason R." <jrdepriest AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygrunsrv -S sshd fails not started
Cc: gga <ggarra AT advancedsl DOT com DOT ar>
In-Reply-To: <Pine.SOC.4.64.0706212030100.11135@libra.sfsu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <1182469846 DOT 20350 DOT ezmlm AT cygwin DOT com> 	 <Pine DOT SOC DOT 4 DOT 64 DOT 0706211653060 DOT 3948 AT libra DOT sfsu DOT edu> 	 <Pine DOT SOC DOT 4 DOT 64 DOT 0706211900290 DOT 11135 AT libra DOT sfsu DOT edu> 	 <467B3A25 DOT 6020706 AT advancedsl DOT com DOT ar> 	 <Pine DOT SOC DOT 4 DOT 64 DOT 0706212030100 DOT 11135 AT libra DOT sfsu DOT edu>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l5MG04jS010313

On 6/21/07, KAYVEN RIESE  wrote:
> On Thu, 21 Jun 2007, gga wrote:
>
> > KAYVEN RIESE wrote:
> >> On Thu, 21 Jun 2007, KAYVEN  RIESE wrote:
> >>
> >>>
> >>> kayve AT kayve-PC ~
> >>> $ cygrunsrv -S sshd
> >>> cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
> >>> 1062:
> >>> The service has not been started.
> >>>
> >
> > Check /var/log/sshd.log.  There's probably more info why it failed there.
> >
> > You can also try starting the daemon manually for testing, as an
> > administrator like (this will output more verbose info to the console):
> >   > /usr/sbin/sshd -d -d -d -D
>
> okay.  shoot.  i was able to connect but when i do the command
> cygrunsrv -S sshd or the other one it still gives the same error.
> how can i make this all happen automatically in the background so
> i don't werry about it?  cron job or something? sheesh, but cygwin
> is a little baby on top of windows or whatever.
>
> >
> > A common cause for that query problem is one of your config files having
> > a wrong configuration, for example.
> >
> > P.S.  Installing openssh on cygwin has been nothing but a huge pain for
> > me, as the docs are mostly worthless.
> >
> > --
> > Gonzalo Garramuņo
> > ggarra AT advancedsl DOT com DOT ar
> >
> > AMD4400 - ASUS48N-E
> > GeForce7300GT
> > Kubuntu Edgy
> >

Hi everybody!  Your first mistake was following directions from two
sites that are not affiliated with Cygwin.  I think the pigtail site
even tells you not to ask for support on the Cygwin mailing lists if
you use his instructions.

Cygwin has excellent documentation for installing sshd right here:
/usr/share/doc/Cygwin/openssh.README in the folder where all of the
Cygwin specific docs for packages are kept.

The most important parts are these:
"If you are installing OpenSSH the first time, you can generate global
config files and server keys by running

   /usr/bin/ssh-host-config"
and
"You can create the private and public keys for a user now by running

  /usr/bin/ssh-user-config

under the users account."

-Jason

-- 
NOTICE:  This email is being sent in clear-text across the public
Internet.  Therefore, any attempts to include unenforceable legalese
restrictions are ridiculous and pointless.  If you can read this,
consider yourself authorized (whether I like it or not).

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/