John Hester wrote:
The default umask may be someplace like /etc/profile or /etc/default/login depending on your platform. Permissions on files created by OUJ logins on our system appear to be determined by the .profile of the UOJ login though. Don't know why yours would be different.
The UOJ login does not have a home directory or a shell. You can't actually log in with that user id and get to a unix prompt. So no .profile for that user. I still don't get how umask could do this-- it only subtracts from the existing permissions, right? In this case I'm gaining world readable permission. (And I have only a vague grasp of how this all works, anyway.)
umask does subtract permissions, but I think a system with no default umask specified would give full permissions for ugo. My /etc/defualt/login umask is set to 022, which is what I get with files created by non-shell processes, like those run by cron, when I don't explicitly set it differently.
-John
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
