SSH is such a feature rich remote shell that I am surprised that there is something very basic missing. The processing of a server side "setup" shell script *regardless* of whether the user has configured themselves a script to run. /etc/sshrc is exactly what I am looking for *except* that it is ignored if the user has a ~/.ssh/rc file. I would like a server side script that is run regardless of what the user has configured for themselves. This would be the equivilent of /etc/profile for local bourne shell logins. What is the reasoning of the "or" relationship between /etc/sshrc and ~/.ssh/rc? Why not an "and" relationship? I am willing to hack ssh to make this an and relationship if it is determined to be a good thing and will be rolled back into the distribution. Thots? b. -- Brian J. Murrell [EMAIL PROTECTED] BCTel Advanced Communications 604 454 5279 Vancouver, B.C.
