Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040831123205.03422e28@pop.prospeed.net> X-Sender: Date: Tue, 31 Aug 2004 12:35:57 -0400 To: "Cary Lewis" , From: Larry Hall Subject: RE: ssh - no access to /dev/st0 In-Reply-To: <536E63F3472B3F4486A01F301164FEC8584DDB@mccmsrv.mccnet.mobi lecom.com> References: <536E63F3472B3F4486A01F301164FEC8584DDB AT mccmsrv DOT mccnet DOT mobilecom DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 12:24 PM 8/31/2004, you wrote: >The issue is that during command line execution of a tar command, sshd >has not set the environment properly, namely the mount points are not >there, so /dev/st0 does not exist, and the PATH variable does not point >to the correct cygwin files either. > >What might be causing this. > >It works fine with an interactive ssh session (providing auto logon is >not set up). > I think it's time to start over on this one too: >Problem reports: http://cygwin.com/problems.html You might want to run your server in debug mode and see if you can spot the problem here. My WAG is permissions problems on ~/.ssh and/or log files/directories and/or 'sshd' isn't running with all the permissions it needs. But that's just guessing. The debug output should help ferret out the real answer. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/