[Bug 834] timezone settings on irix lost

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=834

           Summary: timezone settings on irix lost
           Product: Portable OpenSSH
           Version: 3.8p1
          Platform: All
        OS/Version: IRIX
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sshd
        AssignedTo: openssh-bugs at mindrot.org
        ReportedBy: ktaylor at daac.gsfc.nasa.gov


This may or may not be a bug, but it's different behavior between older sshd's
and the current.

I noticed after installing openssh3.8p1 on IRIX that the TZ environment variable
is not being set, so everything is appearing in GMT...and this is not the case
on linux.

I made a manual change to /etc/profile and specifically set TZ=EST5EDT and this
solves the problems for interactive logins, however, noninteractive logins don't
process this.

I ran this command on an irix and a linux box to see what was being set:
ssh hostname "export"

IRIX:

DISPLAY=localhost:10.0
HOME=/root
LOGNAME=root
MAIL=/usr/mail//root
PATH=/usr/sbin:/usr/bsd:/sbin:/usr/etc:/usr/bin:/usr/bin/X11:/usr/LOCAL/ssh/bin:/usr/LOCAL/bin:/usr/local/bin:
PWD=/root
SHELL=/bin/ksh
SSH_CLIENT='xxx.xxx.xxx.xxx 53599 22'
SSH_CONNECTION='xxx.xxx.xxx.xxx 53599 xxx.xxx.xxx.xxx 22'
USER=root

Linux:

declare -x DISPLAY="localhost:11.0"
declare -x HOME="/root"
declare -x LOGNAME="root"
declare -x MAIL="/var/mail/root"
declare -x OLDPWD
declare -x
PATH="/usr/sbin:/usr/bsd:/sbin:/usr/etc:/usr/bin:/usr/bin/X11:/usr/LOCAL/ssh/bin:/usr/LOCAL/bin:/usr/local/bin:/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="xxx.xxx.xxx.xxx 53604 22"
declare -x SSH_CONNECTION="xxx.xxx.xxx.xxx 53604 xxx.xxx.xxx.xxx 22"
declare -x USER="root"

It seems that neither OS sets TZ when doing a noninteractive login, but IRIX
displays in GMT and linux in EDT.

I'm not sure if this is a bug, or misconfiguration (I haven't made any changes
to our general configuration between openssh3.6 and 3.8).

Thanks for your help. You've all been very helpful in getting these issues resolved.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.