ssh 3.8 and UTC and syslog time don't match

[Donny Jekels]

ssh 3.8p1,ssl097d,zlib121

1. it logs to syslog, but the time stamp is in Greenwich Mean Time (aka GMT, aka UTC), not local time. One work around for this that I can think of is to move the machines to England. And have the staff follow soon thereafter.
2. The other problem is it writes to entries to wtmp for each login. One of the entries is a normal entry. The other shows login duration of 00:00.

any ideas how to fix this?

[Steven E. Protter]

I'm assuming the TZ variable is set on this machine.

Since its 3.8 that means we're off the depot reservation.

My suggetion, seriously is go with a release that HP ported and vetted.

http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA

Okay, you don't like that. Check the environment variables, go to http://www.openssh.org and see if anyone else has this issue. There may be resolution there.

SEP

[Donny Jekels]

opensource rocks.

I shall keep my comments on vendor released open source sw.

thanks, I will look inot the var at compile time.

[Andrew Cowan]

I have to say I agree with Donny there. The usual problem with cron is that it is not restarted after the timezone has been changed.

Try gracefully stopping the cron daemon, then check the TZ settings, an restart. Your should then find your timestamps are correct.

As for the NULL timestamp, I can only guess that you've compiled against the wrong version of HP-UX, or need an OS Patch.

[Jeroen Peereboom]

Donny,

nice workaround. Greenwich is a nice tourist attraction (but as a Dutch citizen: a bit expensive).

;-)

JP