On Sat, Jun 18, 2005 at 10:37:25PM +0200, martin f krafft wrote: > also sprach Alexander Gattin <[EMAIL PROTECTED]> [2005.06.18.2229 +0200]: > > Then, I run login: > ... as I said in the bug report: it works *only* through login...
Thus, here: > [new login, after changing /etc/profile and /etc/login.defs as shown] > [EMAIL PROTECTED]:~$ egrep -i '00(07|22)' /etc/profile ~/.bash_profile > +/etc/login.defs > /etc/profile:#umask 0007 > /etc/login.defs:UMASK 0007 > [EMAIL PROTECTED]:~$ umask > 0022 you have just used `su`/`su -`? > > This is the actual reason why login.defs should be obsoleted > > sometime in favor of pam_umask or similar. > > Absolutely. Yes, but while login.defs can't catch all entries of a user to system (like through cron/at/ssh etc.) which shellrc can catch, it _can_ still catch entries of user with a non-shell (pppd) or with a shell which don't set umask (tcsh in Debian by default, AFAIS). Thus currently UMASK in login.defs _has_ some use. That's why I think it's not a right time yet to remove it from there. > You were making the assumption that I have no clue > what I am talking about. You just were not completely clear, at least I didn't understand some your points. -- WBR, xrgtn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
