Time Zone problmes

[remus]

Hi all,

I think I may have a time zone problem on my backup server.

I'm using rdiff-backup to make backups from windows workstations to a server running microcore 3.8.4 which is running samba and rdiff-backup and rdiffweb.

I have remastered a microcore 3.84 boot cd that includes boot code tz=EST-10 Which is for Brisbane.

Using the Date command on the server gives the following
Tue Feb  3 17:17:24 UTC 2015
Which is the correct time and date for Brisbane.

My windows workstation is also set to +10 Brisbane as its timezone.

My problem is that rdiff-backup is reporting 10 extra hours in the time it takes for a backup. So for example if the backups takes 1min 30 seconds. It says it took 10 hours 1 minute and 30 seconds.

Wondering what I can do to rectify this ?

Thanks,
Remus

[curaga]

Looks like your TC box thinks that is UTC time, not Brisbane time - the date command should print EST instead of UTC. Double-check that what the bios clock is set to matches the UTC status (if utc, no other bootcodes; if local, "noutc" should be there).

[remus]

Thanks curaga,

I've remastered my mc 3.8.4 boot cd with the following.
sudo sh qremaster -t 50 -H syslog= waitusb=8 nodhcp= noautologin= showapps= noutc= tz=EST-10 mc3.8.4.iso output.iso

When the system is booting it states EST-10 where it used to say UTC

date command now produces the following.
Wed Feb  4 15:18:19 EST 2015
Which is the correct time for Brisbane/Australia atm.

By the way is it hard to get tc/mc to get the correct date and time from a server online somewhere ?
I don't actually do this for windows, as it has caused problems in the past. Is it possible to do this with mc with some stability ?
Any reference or tips much appreciated.

Thanks,
Remus

[curaga]

In current versions there's NTP, and before gettime.sh used the old time protocol. I don't remember what was in 3.x unfortunately.

[bmarkus]

In current versions there's NTP, and before gettime.sh used the old time protocol. I don't remember what was in 3.x unfortunately.

In 6.0 the BusyBox ntpd is available. ntp server is configured in /etc/sysconfig/ntpserver.

Previously the old, obsolate DAYTIME protocol was used.

[remus]

I can remaster a mc 6.0 x86 iso and test it with my existing tce folder.

When I have time I'll test compatibility with some extensions I use/maintain for inclusion in 6.x repos.

Thanks,
Remus.

[remus]

Am testing ntp in virtual box before deploying to our server.

Booting stock mc6.0.iso produces wrong time, but the correct date. So I'm guessing that mc does not know my time zone.
So booting stock mc6.0.iso using boot codes "mc noutc tz=EST-10" produces wrong time but correct date.

I'd appreciate a little guidance

Thanks all

[remus]

have just noticed that if I manually use boot codes "mc noutc tz=EST-10" a date command in mc states EST-10 however trying to use qremaster to remaster the mc6.0 iso with command
$ sudo sh qremaster -t 50 -H syslog= waitusb=8 nodhcp= noautologin= showapps= noutc= tz=EST-10 mc6.0.iso output.iso
does not work, where as it has worked on mc 3.8.4 iso's. Has something changed ?