Thanks for the quick response from Mike Matthews (included below). I did
look at the man page, but it didn't quite sink in. rsh -n fixes the
problem. The list comes through again.
Feeling happy but silly,
==============================================================================
David R. Courtade
System Administrator
Amherst Systems Inc.
30 Wilson Rd.
Buffalo, N.Y. 14221
Phone: (716)631-0610
FAX: (716)631-0629
Email: drc_at_amherst.com
>From matthewm_at_sgate.com Thu Jun 27 09:58:39 1996
Date: Thu, 27 Jun 1996 09:55:03 -0400 (EDT)
From: Michael Matthews <matthewm_at_sgate.com>
To: David R Courtade <drc_at_amherst.com>
Subject: Re: Problem in sh - while and rsh
On Thu, 27 Jun 1996, David R Courtade wrote:
> Good Morning (here),
> I have a bit of a problem with DU 3.2c, and 3.0. I have a shell script
> which reads a file and then does an rsh ( it's used for dumps, if you
> care). I read the file in a while loop. The loop works fine without the
> rsh, but if there is an rsh in the while loop the next read is null.
> Anybody have any clue if I'm doing something wrong: I'll include an
> example of the script, and the file read:
rsh eats up the rest of stdin. To fix, just rsh -n.
---
Mike Matthews, Mike_Matthews_at_sgate.com (NeXTmail accepted)
PGP public key available on request
Received on Thu Jun 27 1996 - 16:51:11 NZST