Anton Aylward wrote:

Joachim Schrod said the following on 07/19/2011 10:44 AM:

...

...

...

Yes, it can be overridden on a per user basis with the TZ environment variable. Check to see if you have that set.

...

TZ is not relevant as it is not set during boot, when /etc/init.d/{boot.clock,ntpd} are run.

100% true and 100% beside the point.

As I said .... there is the system level setting, but once a user logs in he may not be in the same time zone as the machine and will need to be able to over-ride the timezone for his session.

Since the time the user sees, the time that Roger sees, is when he logs in and runs commands,

Anton, you should read Roger's, Per's and mine postings again. This is not about interactive observation of time with commands that are run after login. We're talking about syslog timestamps that were made during boot, actually the exact timestamp in the syslog message that ntpd has been started. This timestamp is 2 hours off. In addition, specifically I have posted a series of steps to check proper working of /etc/init.d/boot.clock, to analyse the root cause of that wrong timestamp in the ntpd startup syslog message. This has nothing to do at all with any interactive commands. Roger's issue is definitively not a problem of user commands that are issued on any command line. syslog doesn't care about any TZ value, definitively; I hope we don't have to argue about that. Since the error already appears in syslog timestamps during system startup, any search for problems in his interactive command-line setup is misleading and distracts from his problem's real root cause. And thus I'm not 100% beside the point. $\qed$ ;-) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org