System "wget"command

Mike Schwartz mschw at athenet.net
Tue May 15 16:34:13 PDT 2007


> On Behalf Of Bob Stockler
> 
> Just guessing . . .
> What if you add:
>   >/dev/null 2>&1
> to the end of your 'wget' command ???

   Jay suggested trying that, too.  I'll test that, just in case it provides
some different result than:

1> /dev/null 2>/dev/null

   The "&" did give me another thought, though.  I wonder if I add an "&" at
the end of the command, if that would throw the process into "background"
and eliminate the errors?  (I believe that "SYSTEM" already runs the
commands in background, but I'll grasp at any straw that might fix this.)

   The frustrating thing is that I have can run this dang thing 100 times
and not see an error, then all of a sudden I get a splash.  It may be
relative to the load on the processor at any given time, because the
keypunchers said that they notice this happening more often "when the system
is slow".  

   If I can't come up with anything else, I think I'll try setting this up
as a "USER" function, and test it that way.

Mike



More information about the Filepro-list mailing list