|> I noticed that if i open a |> terminal session, check the umask, it will not be set according to |> what i put in /etc/profile or /etc/login.defs. If, however, i su - |> into the same user, i see th correct umask. That leads me to the |> guess that kde sets a umask differently and independant of the |> login / standard umask. So the precise question would be: Where can |> i define a system wide umask for kde sessions?
Isn't it true that the shells run by terminal-emulators in KDE are not login shells? By default, at any rate. If that's the case, then the user's local configuration files will not be sourced, nor, I think, /etc/login.defs nor /etc/profile. When a bash shell that is not a login shell is started, it reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. Is there a umask value defined in these files? Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
