Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <3BB4D693.76F8F97C@cportcorp.com>
Date: Fri, 28 Sep 2001 15:59:15 -0400
From: Peter Buckley <peter.buckley@cportcorp.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: inconsistent inetd rsh behavior with unc paths
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.

TIA, 
Peter Buckley

-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--

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

