Re: Checking network status as .mpkg requirement
Re: Checking network status as .mpkg requirement
- Subject: Re: Checking network status as .mpkg requirement
- From: Chris Adamson <email@hidden>
- Date: Fri, 29 Jan 2010 11:40:28 -0500
Fair enough, but using ping -t doesn't fix the problem: the requirement always fails, whether the pass value is set to "true" or "false".
It's possible that sending arguments in a script command like this is illegal, but even no-arg scripts like "/bin/pwd" fail in all cases.
I'm about ready to conclude that "result of script" as an .mpkg requirement has no meaningful functionality and cannot actually be used.
--Chris
On Jan 29, 2010, at 11:09 AM, Chris Devers wrote:
> On Fri, Jan 29, 2010 at 10:55 AM, Chris Adamson <email@hidden> wrote:
>> At least as of 10.6, the -W is a timeout in milliseconds for each ping.
>
> I see. Maybe `ping -t` would be more robust? It exists on 10.5 & 10.6,
> and sets an overall timeout for the command, rather than a specific
> timeout for each ping request. Thus, `ping -t 10` would be roughly
> equivalent to the `ping -c2 -w5000` that you're using.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden