Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!iafrica.com!und.ac.za!peacenjoy.mikom.csir.co.za!news.uoregon.edu!news.sprintlink.net!news.bluesky.net!solaris.cc.vt.edu!newsfeed.internetmci.com!in1.uu.net!news.pdx.oneworld.com!news.orst.edu!OES.ORST.EDU!millerj
From: millerj@OES.ORST.EDU (James Miller)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: additional ping -c problem
Date: 3 Apr 1996 09:32:54 GMT
Organization: Oregon Extension Service
Lines: 21
Message-ID: <4jtgk6$cqu@news.orst.edu>
NNTP-Posting-Host: oes.orst.edu
I have been using a script with ping -c in it with 1.1 for over a year
without a hitch. Recently, I have upgraded to version 2.1. I applied
the patch with the output redirect problem with ping -c. It seems
that if ping -c redirect anything to stdout, the script with die.
Here is an example.
#!/bin/csh -f
echo foo3
/bin/ping -c10 199.2.205.252 >& /tmp/ping.tmp
echo foo2
The output of running this script is foo3 to my screen, followed by
info dumped to /tmp/ping.tmp and then foo2 is never executed! Am I
missing something here? This script will work fine (I see foo2) if no
stderr is sent out to the file, but if my slattach is down, an interface
error is redirected to stderr (/tmp/ping.tmp) and foo2 is never seen.
Is this a problem with the patch, or my idea of shell programming?
-James Miller
millerj@oes.orst.edu