Ricardo Chung wrote:

Did you try to change the timezone from YaST->System->Time and Date? This will adjust the main Clock or default timezone clock.

Yes and it shows the correct time zone, with hardware clock set to UTC. Both the desktop clock and date command show UTC, instead of EDT. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Rodney Baker wrote:

On Sat, 24 Mar 2012 23:13:16 James Knott wrote:

...

Ricardo Chung wrote:

...

Did you try to change the timezone from YaST->System->Time and Date? This will adjust the main Clock or default timezone clock.

Yes and it shows the correct time zone, with hardware clock set to UTC. Both the desktop clock and date command show UTC, instead of EDT.

Unset "Hardware clock set to UTC" and set the clock to local time. I seem to remember reading about this somewhere else, but it was a long time ago (in a galaxy far, far, away...).

Definitely no need for that - keep your system clock in UTC, but set your timezone for displaying time. -- Per Jessen, Zürich (16.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-03-24 13:43, James Knott wrote:

Ricardo Chung wrote:

...

Did you try to change the timezone from YaST->System->Time and Date? This will adjust the main Clock or default timezone clock.

Yes and it shows the correct time zone, with hardware clock set to UTC. Both the desktop clock and date command show UTC, instead of EDT.

Try date command in text mode. Find out if you have a TZ variable defined. What I don't remember is where is the default stored. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk9t9rMACgkQIvFNjefEBxo8FgCglHxro270307Gk2eJdyFAmEBy +JMAn1jCMgR5PZNo99PgdEiQH9Jw6yty =r4if -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

There is a 2nd area "Digital Clock Settings" that also has a time zone setting. Changing this corrected the problem. Why is this here, in addition to the one under "Adjust Date and Time", which apparently doesn't work? James Knott wrote:

Carlos E. R. wrote:

...

Try date command in text mode.

Find out if you have a TZ variable defined.

What I don't remember is where is the default stored.

It shows UTC. However, I went into Yast Date & Time and changed to another time zone and back. The date command now shows the correct time as does the time zone setting in the clock, but the desktop clock still shows the wrong time, off by 4 hours.

BTW, this is KDE.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ruediger Meier wrote:

...

There is a 2nd area "Digital Clock Settings" that also has a time

...

zone setting. Changing this corrected the problem. Why is this here, in addition to the one under "Adjust Date and Time", which apparently doesn't work? Because the user may want to use another time zone than root or all the other system users ...

The system clock is set in Yast. These settings are in the clock that appears on the desktop bar. The same clock has both. After I reset the clock in Yast, the correct time zone was shown, but the wrong time. Even after entering the root password, the one under Adjust date & time didn't do anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-03-24 23:07, Jonathan Dlouhy wrote:

Have you tried NTP?

Ntp does not affect the time zone. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk9uToAACgkQIvFNjefEBxr86QCgprYoeQxY8U6SJe0aWYzpFfYA 6AgAoJD2RcqNyKNAqMKQpA/2RoAMlGCC =agVV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Mar 24, 2012 at 7:32 PM, James Knott wrote:

Jonathan Dlouhy wrote:

...

Have you tried NTP?

Yep, I always configure my computers to use it.  However, that has nothing to do with the problem.  At the moment, the question is what happened to cause this?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

If you're dual-booting, Windows will adjust your time and mess things up. -- JAY VOLLMER I write technical manuals; therefore, I am a manual laborer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Mar 24, 2012 at 10:48:36PM -0500, Jay Vollmer wrote:

On Sat, Mar 24, 2012 at 7:32 PM, James Knott wrote:

...

Jonathan Dlouhy wrote:

...

Have you tried NTP?

Yep, I always configure my computers to use it.  However, that has nothing to do with the problem.  At the moment, the question is what happened to cause this?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

If you're dual-booting, Windows will adjust your time and mess things up.

From my http://www.suse.de/~werner/CMOS-CLOCK-HOWTO:

For Vista[tm] SP2, Windows[tm] 7 and Server 2008 R2 the System Administrator of those Windows[tm] systems could create a file: ---------------------------------- *snip* ------------------------------- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001 ---------------------------------- *snap* ------------------------------- and then double click on it to merge this with the contents of the file above with the Windows[tm] registry. With this it could be possible to use for both those Windows[tm] systems and the Linux system UTC as reference of the CMOS clock. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 10:56:01AM +0200, Herbert Graeber wrote:

Am 26.03.2012 10:40, schrieb Dr. Werner Fink:

...

On Sat, Mar 24, 2012 at 10:48:36PM -0500, Jay Vollmer wrote:

...

[...] From my http://www.suse.de/~werner/CMOS-CLOCK-HOWTO:

For Vista[tm] SP2, Windows[tm] 7 and Server 2008 R2 the System Administrator of those Windows[tm] systems could create a file:

---------------------------------- *snip* ------------------------------- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001 ---------------------------------- *snap* -------------------------------

and then double click on it to merge this with the contents of the file above with the Windows[tm] registry. With this it could be possible to use for both those Windows[tm] systems and the Linux system UTC as reference of the CMOS clock. I have tested this some time ago. Works fine on Windows 7, but fails to switch from/to DST on Vista SP2.

In other words, the user space clock shows the correct local time but the system does not have and DST information of the local time zone or does not use such an information. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 12:27:15PM +0200, Carlos E. R. wrote:

The other trick is to tell Windows 7 not to jump the the time when summer hour comes. This is what I have (and local time in the cmos), but I'm not very happy with it...

When I started Linux this Sunday morning (summer time here was the early hours of Sunday), Linux was displaying the old time, one hour slow. I had to play with "rcntp ntptimeset".

Then I booted Windows, and it also displayed the wrong hour, meaning that the CMOS was not adjusted correctly by Linux (local time). I had to manually adjust it as well.

On next reboot to Linux, this was showing the correct hour.

So I have to wonder about this trick of telling Windows to use UTC in the cmos.

Linux would get the summer time information correct, as it does on my Linux only machines. But will Windows do the same, or do I have to adjust it manually?

With Linux the reference for the kernels system clock is UTC. Otherwise time zone data files like /etc/localtime and below /usr/share/zoneinfo will not work. A possible TZ variable is identical to one of the files (including the sub directory) below /usr/share/zoneinfo. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-03-26 13:25, Dr. Werner Fink wrote:

...

...

With Linux the reference for the kernels system clock is UTC. Otherwise time zone data files like /etc/localtime and below /usr/share/zoneinfo will not work.

That's irrelevant once booted, the system doesn't need to know if

Carlos E. R. wrote: the cmos

...

was local or utc.

Whatever is in the CMOS doesn't affect the kernel's system clock. That is UTC as Werner said. (sorry for double-post) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-03-26 15:20, Dave Howorth wrote:

Dave Howorth wrote:

...

Whatever is in the CMOS doesn't affect the kernel's system clock. That is UTC as Werner said.

This thread's been going long enough that perhaps it's worth restating the clocks:

(1) hardware/CMOS/BIOS clock - only used at booting. Should normally be UTC but some versions of Windows required it to be set in the local time of the administrator.

Actually, (almost) all windows versions. W7 and W2k8 apparently accept utc, with a hidden regedit variable. I knew of this variable at least a year or two ago, but the documentation I found of it was discouraging, warned of other problems.

(2) kernel's internal time - always UTC

(3) system-wide time - should be set to the time zone of the machine that is running the system

(4) user time - individually set to the local time of each individual user - defaults to the system time

All correct. :-)

N.B. That's for a computer kept in a single place, though possibly with users around the world. I don't know what the convention is on a mobile computer, though (1), (2) and (4) are unchanged.

For Linux, no change, you only need to change the timezone of the user, at the place he is. For Windows, the clock changes, and the cmos too. A nightmare if you double boot. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk9wb10ACgkQIvFNjefEBxptmQCg3H5AzOvNXhK3QDjv0NNvVzzv f9YAoL/vazSx6U5Dv+IT//Jo/eyRVgTA =skbY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 26 Mar 2012 23:50:30 Dave Howorth wrote:

Dave Howorth wrote:

...

Whatever is in the CMOS doesn't affect the kernel's system clock. That is UTC as Werner said.

This thread's been going long enough that perhaps it's worth restating the clocks:

(1) hardware/CMOS/BIOS clock - only used at booting. Should normally be UTC but some versions of Windows required it to be set in the local time of the administrator.

(2) kernel's internal time - always UTC

(3) system-wide time - should be set to the time zone of the machine that is running the system

(4) user time - individually set to the local time of each individual user - defaults to the system time

N.B. That's for a computer kept in a single place, though possibly with users around the world. I don't know what the convention is on a mobile computer, though (1), (2) and (4) are unchanged.

Right. And I'll keep running mine the way I always have - system clock set to local time, Linux and Windows happy (on the laptop - Windows on the desktop only in VirtualBox), both handling Daylight Savings Time absolutely fine with no errors, and multiple timezones configured for display on the desktop clock(s) (yes - multiple analog clocks for different time zones on my desktop) for easy reference or moving between timezones. Never had a problem - even with bootup filesystem checks. Well - only on one laptop with a stuffed motherboard battery that is impossible to get to and that keeps resetting its system clock to 1/1/2000 if it is unplugged for more than about 10 minutes :-(. -- ========================================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ========================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 10:18:22AM -0400, James Knott wrote:

Dave Howorth wrote:

...

N.B. That's for a computer kept in a single place, though possibly with users around the world. I don't know what the convention is on a mobile computer, though (1), (2) and (4) are unchanged.

Windows computers, on a domain, are tied to the local time of the domain controller. This means if you log into a domain on the other side of the country, your clock will be wrong. I experienced that at IBM, where I had access to the various domains across Canada. As I moved from domain to domain, my computer clock changed time accordingly. With Linux & UNIX, your clock stays put on whatever time zone you configured it for. Which method is better, depends on your needs. If you're a business traveler, who frequents various corporate locations across the country, you might want your computer to be on local time. However, at least until recently, Windows file times were always local time, which means that you'd have to know which time zone it was created in, to know if it was created before or after a file from a different time zone.

BTW, I see you're in the UK, where you'd have only one time zone. In Canada, there are 6 time zones spanning 5.5 hours, across the country.

Hmmm ... what is wrong with using TZ or even reconfiguring /etc/localtime? The problem is that the system clock of the Linux kernel is in UTC which requires to run mkinitrd with the domain approach. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 10:30:50AM -0400, James Knott wrote:

Dr. Werner Fink wrote:

...

Hmmm ... what is wrong with using TZ or even reconfiguring /etc/localtime? The problem is that the system clock of the Linux kernel is in UTC which requires to run mkinitrd with the domain approach.

My point is that with Linux, you have to adjust the time zone if you travel the country and want the computer to show local time. With Windows, it happens automagically. As I pointed out, it's also a disadvantage if you log into a domain in another time zone. Having file times in UTC is always an advantage.

You may fill out a feature request for the next openSUSE to be able to modify the /etc/localtime link accordingly to the current network domain. That would be a win (IMHO), wouldn't it? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 04:05:00PM +0100, Dave Howorth wrote:

Dr. Werner Fink wrote:

...

On Mon, Mar 26, 2012 at 10:30:50AM -0400, James Knott wrote:

...

...

Hmmm ... what is wrong with using TZ or even reconfiguring /etc/localtime? The problem is that the system clock of the Linux kernel is in UTC which requires to run mkinitrd with the domain approach. My point is that with Linux, you have to adjust the time zone if you

Dr. Werner Fink wrote: travel the country and want the computer to show local time. With Windows, it happens automagically. As I pointed out, it's also a disadvantage if you log into a domain in another time zone. Having file times in UTC is always an advantage.

You may fill out a feature request for the next openSUSE to be able to modify the /etc/localtime link accordingly to the current network domain. That would be a win (IMHO), wouldn't it?

I don't think there's any need for a feature request. I believe DHCP option 2 sets the time offset from UTC of a client machine. But it's deprecated; I don't know what the current recommended technique is.

AFAICS from specs there will be the timezone offset which leads to zoneinfo files below /usr/share/zoneinfo/Etc/ like Etc/GMT[+-]<offset> ... Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 05:09:24PM +0200, Lars Müller wrote:

On Mon, Mar 26, 2012 at 04:42:03PM +0200, Dr. Werner Fink wrote:

...

On Mon, Mar 26, 2012 at 10:30:50AM -0400, James Knott wrote:

...

Dr. Werner Fink wrote:

...

Hmmm ... what is wrong with using TZ or even reconfiguring /etc/localtime? The problem is that the system clock of the Linux kernel is in UTC which requires to run mkinitrd with the domain approach.

My point is that with Linux, you have to adjust the time zone if you travel the country and want the computer to show local time. With Windows, it happens automagically. As I pointed out, it's also a disadvantage if you log into a domain in another time zone. Having file times in UTC is always an advantage.

You may fill out a feature request for the next openSUSE to be able to modify the /etc/localtime link accordingly to the current network domain. That would be a win (IMHO), wouldn't it?

Why? With both major desktop environments it's possible set additional time zones. For lxde it looks like the use of gnome-time-admin is the suggested solution.

Ok, I must admit I've not tested this with Gnome 3. But this worked with Gnome 2 on openSUSE 11.4.

With KDE as of openSUSE 12.1 this is to achieve via a right mouse click to the clock -> timezones -> add ticks as you need.

This is not system wide and only for Gnome/KDE users and does not touch any already running programs. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 05:45:02PM +0200, Lars Müller wrote:

Gnome/KDE/LXDE. This I gues covers more than 80% of our users.

And you know the 80/20 20/80 rules. You need 80% of your time to implement the missing 20%.

uucp I guess is used by 0.02% of the UNIX users today. But it's good to keep it going!

It works, that's it.

fvwm2 is used by 0.47% of the UNIX users today. Therefore it even makes 23.5 times more sense to keep it!

+1 Beside this stupid desktop discussion I've found related to the subject -> https://www.ietf.org/rfc/rfc4833.txt The question is if our dhcp servers and clients together with our dhcpcd-hool and netconfig scripts would be able to use this. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 03:03:01PM +0200, Carlos E. R. wrote:

On 2012-03-26 13:25, Dr. Werner Fink wrote:

...

With Linux the reference for the kernels system clock is UTC. Otherwise time zone data files like /etc/localtime and below /usr/share/zoneinfo will not work.

That's irrelevant once booted, the system doesn't need to know if the cmos was local or utc.

You missed my point Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Mar 26, 2012 at 10:40:48AM +0200, Dr. Werner Fink wrote: [ 8< ]

From my http://www.suse.de/~werner/CMOS-CLOCK-HOWTO:

For Vista[tm] SP2, Windows[tm] 7 and Server 2008 R2 the System Administrator of those Windows[tm] systems could create a file:

---------------------------------- *snip* ------------------------------- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001 ---------------------------------- *snap* -------------------------------

Move this document to the wiki, please. Then it's more likely for Lieschen Müller and Joe Doe to find it. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Mon, Mar 26, 2012 at 01:42:09PM +0200, Dr. Werner Fink wrote:

On Mon, Mar 26, 2012 at 12:47:51PM +0200, Lars Müller wrote:

...

On Mon, Mar 26, 2012 at 10:40:48AM +0200, Dr. Werner Fink wrote: [ 8< ]

...

From my http://www.suse.de/~werner/CMOS-CLOCK-HOWTO:

For Vista[tm] SP2, Windows[tm] 7 and Server 2008 R2 the System Administrator of those Windows[tm] systems could create a file:

---------------------------------- *snip* ------------------------------- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001 ---------------------------------- *snap* -------------------------------

Move this document to the wiki, please. Then it's more likely for Lieschen Müller and Joe Doe to find it.

It is not my job to write Wiki pages not I've the time to do.

But you have the time to answer here? You have the time to maintain uucp in the year 2012? One emacs package less was the first and appreciated step forward. The second one will follow, I hope. ;)¹

The HOWTO from above is simply a copy I've written from scratch for one of the several SLES bugs with local time in CMOS.

Simpyl copy and paste it to the Wiki and let the community help you to make it look well as it was done with http://en.openSUSE.org/Mailman for example. I as part of this community offer you help. That's all I can offer you. Keep in mind SUSE is part of this community, please.

IMHO a short version should become part of YaST and poped up if an installer has local time in its CMOS/hardware/firmware clock.

First we need a Feature request and have to discuss it three years. I'm sure at some point in time even you'll understand how important a more community driven approach. For the future of openSUSE, SUSE, and SLE. Maybe even for your own future. Cheers, Lars ¹ This is a smily an the intention of it is to even you smile. -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

James Knott said the following on 03/24/2012 04:29 PM:

Carlos E. R. wrote:

...

Try date command in text mode.

Find out if you have a TZ variable defined.

What I don't remember is where is the default stored.

It shows UTC. However, I went into Yast Date & Time and changed to another time zone and back. The date command now shows the correct time as does the time zone setting in the clock, but the desktop clock still shows the wrong time, off by 4 hours.

Did you log out then log in again so that the value of TZ was reset in your environment? -- "Quality refers to the extent to which processes, products, services, and relationships are free from defects, constraints and items which do not add value." - Dr. Mildred G Pryor, 1995 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Sat, 24 Mar 2012, Carlos E. R. wrote:

Find out if you have a TZ variable defined.

What I don't remember is where is the default stored.

/etc/localtime is a copy of or a symlink to the timezone-file under /usr/share/zoneinfo. /etc/init.d/boot.clock actually unsets TZ, so by default TZ is not set and /etc/localtime used. ==== man 3 tzset ==== If the TZ variable does not appear in the environment, the tzname vari- able is initialized with the best approximation of local wall clock time, as specified by the tzfile(5)-format file localtime found in the system timezone directory (see below). (One also often sees /etc/localtime used here, a symlink to the right file in the system timezone directory.) ==== $ oTZ="$TZ"; unset TZ; strace -eopen date 2>&1 | grep -v lib; TZ="$oTZ" open("/etc/ld.so.cache", O_RDONLY) = 3 open("/etc/localtime", O_RDONLY) = 3 Mon Mar 26 05:25:15 CEST 2012 $ strace -eopen date 2>&1 | grep -v lib open("/etc/ld.so.cache", O_RDONLY) = 3 open("/usr/share/zoneinfo/right/Europe/Berlin", O_RDONLY) = 3 Mon Mar 26 05:25:37 CEST 2012 $ TZ=UTC strace -eopen date 2>&1 | grep -v lib open("/etc/ld.so.cache", O_RDONLY) = 3 open("/usr/share/zoneinfo/UTC", O_RDONLY) = 3 Mon Mar 26 03:26:27 UTC 2012 FWIW, I set TZ in /etc/profile.local. HTH, -dnh -- O'Neill: [on Freyr] This little feller is about three feet tall, got clammy grey skin, big black eyes, and skinny, tiny little arms and legs like toothpicks. -- Stargate SG-1, 5x05 - Red Sky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Mon, 26 Mar 2012, Carlos E. R. wrote:

On 2012-03-26 05:30, David Haller wrote:

...

FWIW, I set TZ in /etc/profile.local.

Interesting. Doesn't the default system work for you?

It works, but I've been using that profile.local for years (and I should clean it up, there's stuff in there from my SuSE 6.2 ;) -dnh -- Yah. Spam, spam, spam, cuisson de cerf haché au sauce truffe, and spam. -- Richard Bos on french "hypermarkets" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org