1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

@ping behavior change

Discussion in 'Support' started by Peter Bratton, Nov 14, 2011.

  1. Peter Bratton

    Joined:
    Jul 1, 2008
    Messages:
    81
    Likes Received:
    0
    After updating to v13.01.029, @ping started giving me "incorrect parameter" errors this morning, from a btm file that has been running well for years. The command is
    Code:
    set var=%@ping[192.168.1.21,1,64]
    After some fussing around, I discovered that the timeout argument is the culprit. If I leave it out
    Code:
    set var=%@ping[192.168.1.21,,64]
    , the function works, and surprise, if I put it between double quotes
    Code:
    set var=%@ping[192.168.1.21,"1",64]
    it also works but if the target doesn't respond, the function waits well past the specified 1-second timeout.
    --
    Peter
     
  2. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,784
    Likes Received:
    29
    It seems to work correctly with timeouts greater than 11 (but 11 seconds is
    quite a while to wait for a ping response).

    On Mon, 14 Nov 2011 11:51:05 -0500, Peter Bratton <> wrote:

    |After updating to v13.01.029, @ping started giving me "incorrect parameter" errors this morning, from a btm file that has been running well for years. The command is
    |Code:
    |---------
    |set var=%@ping[192.168.1.21,1,64]
    |---------
    | After some fussing around, I discovered that the timeout argument is the culprit. If I leave it out
    |Code:
    |---------
    |set var=%@ping[192.168.1.21,,64]
    |---------
    |, the function works, and surprise, if I put it between double quotes
    |Code:
    |---------
    |set var=%@ping[192.168.1.21,"1",64]
    |---------
    | it also works but if the target doesn't respond, the function waits well past the specified 1-second timeout.
     
  3. Peter Bratton

    Joined:
    Jul 1, 2008
    Messages:
    81
    Likes Received:
    0
    Indeed, that pretty much defeats the purpose of the timeout argument.
    The function works if the timeout argument is 0, but it waits the default 5 seconds anyway.
    --
    Peter
     

Share This Page