This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: sshd as service without /usr/bin being in the system path.

> -----Original Message-----
> From: Igor Pechtchanski []
> Sent: 13 May 2003 16:10
> To: Steve Fairbairn
> Steve,
> You can specify the path in cygrunsrv's -e option...  
> However, note the
> marked lines from "cygrunsrv --help":
>   -e, --env <VAR=VALUE>     Optional environment strings 
> which are added
>                             to the environment when service 
> is started.
>                             You can add up to 255 environment 
> strings using
>                             the `--env' option.
> --->                        Note: /bin is always added to 
> $PATH to allow all
> --->                        started applications to find at 
> least cygwin1.dll.
> so it looks like you don't even need to do that (/bin and 
> /usr/bin are the
> same under Cygwin).
> 	Igor

Thanks Igor,

I should've spotted this given the fact that the ssh-host-config script uses
-e when it installs the service.

I have another issue with my sshd service and I can't find anything like it
in the archives.  The service is installed fine.  I can go to it in services
and stop and start it perfectly.  Once I've started it, I can ssh to the
server from my machine with no problems (I am ssh'ing to the same user the
server is actually logged in as.  I only ever use that one user on the
server running sshd).

The service is set to start automatically, and if I reboot the server and go
to servics in control panel, it's all there started fine.  If I try and
connect to it however, the connection is made and I get the prompt for the
users password, but the password is always incorrect.  If I use control
panel->services to stop and start the service again, then I am able to
login.  I have no idea what is different between the service running from
boot, and the service stopped and started by the logged in user.

I have attached ssh -v logs from both a failed connection and a successful
one.  If anyone has any suggestions, I'd be most grateful.




This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 


Attachment: ssh-succeed.txt
Description: Text document

Attachment: ssh-fail.txt
Description: Text document

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]