WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: interesting timezone requirement  (Read 1948 times)

Offline onelife

  • Full Member
  • ***
  • Posts: 141
interesting timezone requirement
« on: February 20, 2019, 11:17:27 AM »
Hi forum,

Having searched and search I seem to find all the answers for keeping your system time in sync with NTP (as that's what it does ;) )

BUT here's a random question - How can I keep in sync with a ntp server but then offset that time by a constant value such as say 1 minute ahead.

Yes, that's odd - but essentially I have a system that's powering a audio stream that has an almost constant 1 minute buffer.

So, I'm trying to find a way that I can accommodate this buffer time in the system time so that audio you hear is then closer to the real world time.

I know I could set time / date with "date" - but that involves losing the benefit of keeping the clock in some sort of "sync".

Not sure if this is possible in anyway? I looked at timezones but that obviously only helps with large jumps in time where as all I'd like to achieve is a system time 1 minute faster than ntp time it gets?

Not sure if there's any magical ntp.conf setting I've missed?

There was the thought to only use GetTime.sh and add a delay in time form when that script gets the value and then actually sets the value on the system?

But thought best I see if anyone has ever needed this type of strange time setup before :)

Many Thanks.




Offline onelife

  • Full Member
  • ***
  • Posts: 141
Re: interesting timezone requirement
« Reply #1 on: February 20, 2019, 11:45:48 AM »
okay, so I'll answer my own question as seems you can set minute in TZ boot option. I've not tried yet but found this in more detail.

https://www.di-mgt.com.au/wclock/help/wclo_tzexplain.html

So will try and post my findings here.