From: Grant Lowe (GLowe@MedImpact.com)
Date: Wed Aug 14 2002 - 09:35:53 EDT
Hi all.
I got a few replies. Most people pointed me to the fact that this is normal
behaviour for ssh. If I specify a command, ssh runs it in a non-interactive
shell. This means that none of my shell environment controls (.login,
.profile, etc.) will be sourced. So the umask I see in the non-interactive
shell are the system-wide default.
The answer I got is comining the above information with an documented
feature of init. If you take a look at /etc/default/init, there is a line
that reads: CMASK=022. We changed CMASK to 002, ran init q, and now
everything seems to be working.
Original question:
We have a strange one here. If I ssh machinea umask, I get 022. If I ssh
machinea, once I'm logged into the machine and run umask there, the umask is
002, which is the correct umask. Why is ssh getting a different umask?
This is a 420R, running a fully patched Solaris 8, ssh 3.4p1. Will
summarize.
Thanks go to:
Josh Glover [jmglov@incogen.com]
system administration account [sysadmin@astro.su.se]
Galen Johnson [gjohnson@trantor.org]
ed.rolison@itc.alstom.com
Doug Winter [dwinter@icpeurope.net]
grant
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:46 EDT