The problem is that when you use ssh, somehow there is no terminal assigned to your session. You can verify this with the tty command. It should report something like this:
$ tty
/dev/pts/ta
If instead you get something like "not a pty" then your login is non-standard. Are you running ssh similar to remsh, that is, simply running a remote or batch command and not an interactive session with a shell prompt?
If so, that is the problem. There are several commands in your profiles that require a 'real' terminal. Among these are:
stty ttytype tset tput tabs
All of them will report "not a typewriter" when you are connected in batch mode. Now this is a common error because cron jobs and other batch or background jobs that perform a profile'd login will not have a tty/pty device. And the fix is to always protect these terminal-only commands:
if tty -s
then
ttytype -s
stty ...
tabs ...
fi
Now if this conditin exists only when more than 10 users on the system, I would suspect that your maximum pty/tty kernel parameter does not match your device files, or someone has removed one or more of these files. To fix this, run SAM and change the 3 parameters:
npty nstrtel nstrpty
all equal to 70 or so (actual number depends on the maximum number of connections you expect in the future). SAM will change the parameter and also repair the device files.
Bill Hassell, sysadmin