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: <50A89B19AEAAD411B9D200A0C9FB5699B34AA7@craius.cportcorp.com> From: Mark Keil To: cygwin AT cygwin DOT com Subject: inetd->rshd: can't fork; try again Date: Mon, 21 May 2001 14:37:45 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Folks, A google search for the following: inetd service cygwin "can't fork" only turned up one reference that matched that string in the rshd.c included the msg. Now that I have telnetd and rlogind working from inetd as a service, rshd will only return Can't fork; try again. trying again doesn't work though, it also wants another try. An examination of the source shows that that indeed fork must have failed. Any clues why fork would fail if executed rshd? rshd worked if I start inetd.exe from the command line. Also intgeresting is that rshd returns "No remote directory." (aka no home directory) If I am not logged in to the remote NT box. Does this mean that home directories can't be found on an NT box if the user hasn't logged in directly at the screen? Thanks for any info, Mark Keil -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple