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 Message-ID: <20010609001518.19958.qmail@web9806.mail.yahoo.com> Date: Fri, 8 Jun 2001 17:15:18 -0700 (PDT) From: Jonathan Bishop Reply-To: j DOT bishop AT utoronto DOT ca Subject: inetd: install-as-service difficulty To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hello, I recently installed cygwin 1.3.2 utilities including inetutils on the C: drive of an NT4.0 machine. I can run inetd, telnetd and ftpd just fine all in accordance with the inetutils README. However, on E: drive of another similar NT 4.0 (same build/service pack) machine, the inetd --install-as-service command fails to complete, although the cygwin installation seems to be working fine in other respects. Adding the debug option to inetd yields one additional message about Service Manager, but no obvious solution to problem. Strangely, I am able to run inetd from the command line, then telnetd from the command line, and then log in to a telnet session. This seems to contradict the README for inetutils, which says you can only start inetd from command line in Win 95/98. I can't find any mention of how to troubleshoot this in the FAQ, mail archives or inetutils README. Any suggestions appreciated. Is there some known trick within the NT environment variables or user permissions that can block inetd --install-as-service? Thanks, Jonathan Bishop jbishop AT cmed DOT com __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple