I would avoid rsh altogether; I've found it to be buggy, especially with commands which give you significant output. Some of these bugs are mentioned in the rsh manpages, if I recall. It's also relatively insecure. If you are going to run a command on a remote machine, consider Net::SSH::Perl (preferably) or Net::Telnet.
Just my opinion, of course, but these modules have worked extremely well for me for running commands on our cluster. Matt --- Jenda Krynicky <[EMAIL PROTECTED]> wrote: > From: "Alex Harris" <[EMAIL PROTECTED]> > > > exec "rsh $plant /u1/bin/forkit '/u1/bin/zwork.pl'" > > > > How do I use the above, which starts my process then lets my calling > > program continue, to check for an error? In this particular case, the > > error occurs because zwork.pl does not exists on the maching the rsh > > is calling and I need to note this error. > > Would you please read the documentation for exec() ? > > perldoc -f exec > > you want either system() or `` (backticks). Depends on how does > the rsh give you the status. > > Jenda > > =========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== > There is a reason for living. There must be. I've seen it somewhere. > It's just that in the mess on my table ... and in my brain. > I can't find it. > --- me > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
