Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Mark Himsley To: Peter Buckley Cc: cygwin AT cygwin DOT com Subject: Re: inconsistent inetd rsh behavior with unc paths Date: Sat, 29 Sep 2001 13:40:23 +0100 Message-ID: References: <3BB4D693 DOT 76F8F97C AT cportcorp DOT com> In-Reply-To: <3BB4D693.76F8F97C@cportcorp.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On Fri, 28 Sep 2001 15:59:15 -0400 you wrote: >I just wanted to point out something I found while I am >trying to get rsh to work- > >If I have //unc-path/to-my/home as my home directory >in /etc/passwd, I CANNOT rsh to my machine when >inetd is started as a service (whether I start it >or SYSTEM starts it). But if I start inetd from the >command line, rsh works fine. > >I don't know what the intended behavior is for rsh or >inetd, but I don't understand why they work differently >when started as a service or started from the command line. >Maybe an environment thing? If anyone can point me in the >right direction, I think it might help me in my quest to get >rsh working with inetd as a service. Clue: when you run as a service its probably running as the user SYSTEM (check in the Services control panel). When you run it from the command line its running as your you. Does your user SYSTEM have access to your UNC paths? Probably not. -- Mark Himsley In Acton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/