The MultiNet 5.0 doc references "call_dst_proc" that can be placed in
NTP.CONF. The doc states:

> call_dst_proc
>
> Causes the NTP server to spawn a subprocess to execute the
> MULTINET:NTPD_DST_PROC.COM procedure, if such a procedure file exists
> with the proper protections, when changing into or out of DST, or when
> first starting up. See the /"Using the /*/call_dst_proc/*/ //option"/
> below for more information.
>
The additional documentation about the procedure is too lengthy to post
here (you can find it here:
http://www.process.com/tcpip/mndocs/...h14.htm#E29E15)
, but it does say that P2 is the timezone offset in *seconds*, so
Jeremy's case is handled nicely and isn't broken after all. :-) +9:30
would be "+34200" for P2.

- ken
Ken Connelly wrote:

> Jeremy Begg wrote:
>
>> Hi Mike,
>>
>>
>>
>>> $!
>>> $! This procedure is called with 5 parameters:
>>> $!
>>> $! p1 = Timezone_Name - string ("EST", "EDT", etc.)
>>> $! p2 = Timezone Offset - integer ("-5", "-4", etc.)
>>> $! p3 = DST on? - boolean ("Y", "N")
>>> $! p4 = In Twilight Zone? - boolean ("Y", "N")
>>> $! p5 = Startup or DST change? - string ("START" or "DST")
>>> $!
>>>
>>
>>
>> What will the value of P2 be for South Australia (GMT +09:30)?
>>
>>
> broken? ;-)
>
> and I don't have this command procedure on my 5.0 system either.
>
> - ken
>
>> Thanks,
>>
>> Jeremy Begg
>>
>>