- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Umask parameter
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2009 10:20 PM
тАО07-15-2009 10:20 PM
Umask parameter
In my server, i have set umask 022 in /etc/profile. Now when i login to root, it shows umask 022. when i do su - prdadm, it shows me umask 022. but when i directly login to prdadm user, it shows me umask 077. I also set umask in .profile but no luck.
plz let me know, where i have to set umask, so that it remain 022 only for prdadm also.
Ankit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2009 10:39 PM
тАО07-15-2009 10:39 PM
Re: Umask parameter
grep umask ~prdadm/.profile
check if that .profile is calling other scripts like database start or application start.
do a grep on those scripts also.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2009 11:02 PM
тАО07-15-2009 11:02 PM
Re: Umask parameter
Check your .profile again see there is any script is running or not.
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 01:37 AM
тАО07-16-2009 01:37 AM
Re: Umask parameter
Normally umask value will be sourced from /etc/profile unless user's profile will have it's own umask value.
Check the user's profile depends on his shell.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 03:39 AM
тАО07-16-2009 03:39 AM
Re: Umask parameter
echo "starting .profile, umask=$(umask)"
...
echo "finished .profile, umask=$(umask)"
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 02:09 AM
тАО07-17-2009 02:09 AM
Re: Umask parameter
(i.e. what does "grep ^prdadm: /etc/passwd | cut -d : -f 7" report?)
If prdadm's shell is /usr/bin/csh, /usr/bin/tcsh or some other non-Bourne shell, it won't execute /etc/profile or ~/.profile - it runs its own login scripts instead. For csh and tcsh, the standard csh-style login scripts are /etc/csh.cshrc, /etc/csh.login and ~/.cshrc.
If prdadm's shell is e.g. csh and there is no umask command in csh-style login scripts at all, the session might inherit the umask from whatever is the parent process.
When you do "su - prdadm", the parent process is your session, which already has umask 022.
When you login directly to prdadm, the parent process is the network login service: sshd/telnetd/whatever. These are security-critical services, so they are usually hard-coded to set a very strict umask, like 077, unless configured otherwise. If necessary, the strict umask can then be relaxed in /etc/profile, /etc/csh.cshrc or equivalent.
MK