asked on

sync date with NTPd

hello,
I am on EST time using centos v5.7 and right now its 1.56pm I started the NTPd service

service ntpd start
chkconfig ntpd on

then I check and this is what I get

[(12:20 PM)][(root@critical)] [(~)] $ date
Sat Oct 1 12:56:03 EST 2011

how can I fix the date?

Papertrip

The correct timezone currently is actually EDT, and that is why your server is showing 1 hour off.

Change/confirm your timezone by using tzselect

[root@broken etc]# tzselect
Please identify a location so that time zone rules can be set correctly.
<snip>
The following information has been given:

        United States
        Eastern Time

Therefore TZ='America/New_York' will be used.
Local time is now:      Sat Oct  1 14:13:48 EDT 2011.
Universal Time is now:  Sat Oct  1 18:13:48 UTC 2011.
Is the above information OK?

Open in new window

XK8ER

ASKER

that doesnt change the time for the system, this is what I get.

You can make this change permanent for yourself by appending the line
        TZ='America/New_York'; export TZ
to the file '.profile' in your home directory; then log out and log in again.

Here is that TZ value again, this time on standard output so that you
can use the /usr/bin/tzselect command in shell scripts:
America/New_York
[(01:23 PM)][(root@alpha)] [(~)] $ date
Sat Oct  1 13:23:50 EST 2011

Open in new window

ASKER CERTIFIED SOLUTION

Papertrip

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

XK8ER

ASKER

ok, the time is now correct.. now when the time changes into daylight saving.. would it change automatically?

Papertrip

Yes it will.

You may want to restart any applications that could have the old TZ cached. I have never changed the timezone on a server apart from during the install, so I'm not sure of the repercussions of doing it on the live system.

If you are able to reboot the machine, that would be the safest, but is probably unnecessary... your call on that.

XK8ER

ASKER

I think crond would be the only service that needs to restart so that it can rotate the logs right at 4am.. other than that when I change the date its all good.