Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.
Sign up to join this community
I am using a local timezone (non-UTC) on my server. Whenever I update the tzdata via yum, the system resets /etc/localtime to the default file and I am back on UTC.
While #date still shows the proper timezone, CRON and other services switch to UTC.
How can I prevent that?
My CentOS knowledge is a bit out of date, but you may need to also specify the timezone in /etc/sysconfig/clock.
As a last-ditch effort, of course, you could:
chatter +i /etc/localtime
It is surprising that tzdata munges /etc/localtime though. Have you made it a symlink to /usr/share/zoneinfo/...? Are you perhaps updating glibc at the same time as tzdata? (since the glibc package owns /etc/localtime)
sudo ln -s /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime to update the time. After a tzdata update, the time is reset to UTC. After changing the clock to Europe/Amsterdam, this doesn't happen anymore. Maybe this is not the correct way to set localtime, but your answer seems to fix my problem.
I know Im late ;-) All RH based system before version 7 the correct way was to set in /etc/sysconfig/clock
and then run tzdata-update tzdata rpm runs this so that's why it resets it one version 7 we have timedatectl....
/etc/localtimefile and contains no post-install script fiddling with it. (git.centos.org/blob/!!rpms!tzdata.git/…)$ rpm -q --triggeredby tzdata, and you'll see the glibc-common package has a script triggered by tzdata update. Specifically, it runs/usr/sbin/tzdata-update. (This is on CentOS 6 and earlier; things are different with systemd.)ls -l /etc/localtimeandcat /etc/sysconfic/clock?