This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Network drives & ssh access
--On Monday, August 23, 2010 9:41 PM -0400 "Larry Hall (Cygwin)"
<reply-to-list-only-lh@cygwin.com> wrote:
On 8/23/2010 7:47 PM, Quanah Gibson-Mount wrote:
I have a network drive set up to auto-reconnect at startup, which
appears to work fine. If I start cygwin after logging in, I can see the
drive in the /cygwin directory.
However, I cannot see the drive in the /cygwin directory when connecting
via Cygwin's OpenSSH. My guess is that ssh starts before the drive shows
up. Running "net use" from the SSH connection says it is unavailable:
<snip>
The FAQ is your friend:
<http://cygwin.com/faq/faq-nochunks.html#faq.using.shares>
Thanks, I missed that, was reading the fstab etc pages.
So I set up sshd to run as the build user, but it still doesn't work:
I ran:
cygrunsrv.exe -R sshd
confirmed no sshd processes were running
rebooted, confirmed no sshd processes were running
Ran:
ssh-host-config -u build
to set it up to run as the "build" user (my primary user)
Told it to use privilege separation
Said I want sshd to run as a service
Put ntsec tty as the values for the CYGWIN environment variable
Ran "cygrunsrv -S sshd
ps -eaf now shows sshd running as SYSTEM proc 3376 with parent 3340, and a
subprocess
sshd 3444 running as build user
I log in as the build user via ssh, and ps -eaf shows me to sshd process
running as SYSTEM - proc 3376 with parent 3340 and a subprocess 1824 with
3376 as the parent.
So, in reading the further documents, is what I need to do then is change
the SYSTEM entry in /etc/passwd to use the SID of the build user instead?
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
--
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