X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-IronPort-AV:	E=McAfee;i="5200,2160,5241"; a="988212"
From:	"Dang, Robin" <rdang AT qualcomm DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Date:	Thu, 28 Feb 2008 12:09:37 -0800
Subject:	Re: Access to Network Drive under ssh
Message-ID:	<4A27D05E36DE7E47B96BCF7DD8F3FD7101307B3B6D@NASANEXMB04.na.qualcomm.com>
Accept-Language:	en-US
acceptlanguage:	en-US
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id m1SKARnJ015405

http://cygwin.com/ml/cygwin/2006-06/msg00820.html

I am having the same problems as in the discussion and would appreciate any help to resolve it. After I log into a ssh session, the drives are not automatically mapped and typing 'net use' gives me unavailable. I can map them manually, but I need them to be mapped automatically to setup the environment properly for my scripts.

"Anyway, the way I generally get things... well, closer to working, is to create a service that calls 'bash -c <some-sshd-init-script>', and have the script issue a bunch of 'net use <foo> <bar>' commands and then exec sshd. That way you don't have to worry about connections being remembered, because they will always be created for you when sshd starts up."

In the post, there is a workaround for the problem, but I cannot write the sshd-init-script and create the service to run it, so it works. Would anyone provide anymore detail or instructions?

Thank you,
Robin

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

- Raw text -