Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <175601c15ca7$bbb88350$820314ac@fdvlegoll01> From: "Vincent Legoll" To: Cc: "Vincent Legoll" Subject: rsh and -n option vs < /dev/null redirection Date: Wed, 24 Oct 2001 18:19:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Hello all, I'm using cygwin at work to run our build chain (bash + make + rsh + etc...) what I'm doing in a makefile under cygwin/win32 is something like this : RemoteLoop: for host in linux win32 solaris; do \ rsh -l build $$host 'make aTarget VAR1=VAL1' > aFile.txt 2>&1 & \ done I've fought a long time finding why I was receiving "broken pipe" error messages from remote makes. I read messages from your mailing list and begun to suspect a redirection problem from the rsh command, so I tried -n option with no success whereas redirecting rsh's input to /dev/null worked !!! While reading rsh's man page, I thought "-n" or "< /dev/null" would do the same, but it appears not to be the case... Does this scenario make any sense for you ? Perhaps this should be a rsh bug report and not related to cygwin at all... Could you CC me your replies since I'm not subscribed to this list, thanks. -- Vincent Legoll - CM engineer - Peregrine Systems R&D France vlegoll@peregrine.com -- 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/