I am writing a bash script for auditing a Linux System. One of the points to capture is the umask of the users in the system. Though a 'umask' command executed by the respective user gives this value, i am not sure how to get this in a script, which would be run with root credentials. This my be pretty easy, but i am not sure how root can find this for say 'user-x' (except say peeking into /etc/bashrc).
umask doesn't seem to accept username argument like the 'id' command does...
I am using Red Hat Linux 4 .There are some few questions in my mind related to umask. I want to know that is the default file and directory permissions ?
- When we use umask (022) command in terminal. and create a new file then the permissions applied for new file is for that session and when the system will reboot linux will take automatically its default permission from etc/bashrc or /etc/profile ? - Can we make our own umask or the professional way is to follow 022 only ? - What is the benefit of umask in Linux?
My Debian system has by default umask permissions of 0022, which I never liked. One user can read all the files of another seems very insecure to me.
I am planing to set it to 007, so that user and group have rw but all others have none.
Are there any side effects to that? I have noticed from a trial I did where I was changing permissions on the filesystem that some system stuff in the OS does not work anymore, if "others" have no read permission anymore, so that is why I am asking.
And why are chmod / umask permissions sometimes stated as 4 digits? What is this "all" group in the end? Isn't that already covered by "others"?
I'm setting up an application server for a small organization using Ubuntu 10.04 and LTSP. We built a machine with a quad core Athlon II, got a Gigabit swtich, and a couple Gigabit ethernet cards. I burned gPXE into a couple EPROMs and turned their old PIII and Duron systems into thin clients.
So far so good.
Now, I'm trying to set up a shared directory that two users in the same group can both read and write. Let's call it "/home/shared". I want to set UMASK to 007, so that by default, files are created readable and writable by user and group, with no permissions for anybody else. I changed a line in "/etc/profile" from "umask 022" to "umask 007". After rebooting the app server, the umask does appear to be 007 when you log in at the console. However, it doesn't seem to affect the terminals.
So I figured I needed to change it in "/opt/ltsp/i386/etc/profile". vi helped me out with that. Didn't make a difference in the terminals. Ok, I need to rebuild the image, so I did an "ltsp-update-image" and rebooted the terminal. umask is still 022. ???
I changed UMASK in "/opt/ltsp/i386/etc/login.defs" and rebuilt the image. No change. ??? I really don't understand why this isn't working.
How can I change the UMASK for users who log in on an LTSP terminal?
We have users that send files to our server via sftp... We normallyhave umask set to 022 but for these files we would like to force a umask of 002... I've tried to change in the .bash_profile but does not seem to make any difference...
I am building a livecd, the live user created at boot time is a member of the audio group set in /etc/group. This way works for the livecd but when installed a user must manually add himself to the audio group. How can I set new users to automatically become a member of the audio group? In /etc/default/useradd I can set only one group.
How do I enable Adobe Reader as the default reader in Linux automatically whenever I create a new user account? I don't want to find myself doing it for every user I create, It's too tedious if there are too many users.
In other Linux distros I've used, new users are assigned to their own group (i.e. user 'joe', group 'joe') by default. To my surprise, when I create new users with my openSUSE 11.4, they are all assigned to the 'users' shared group by default.To test this, I created a new user called 'friends'. From my terminal, I can see how the new user files look like:
joe@linux:~> ls -l /home/friends/ total 40 drwxr-xr-x 2 friends users 4096 Sep 3 11:37 bin
I have 2 Oracle users that generate .tmp files under /var/tmp. By default, the files have the permissions 644. Now, a need has arisen whereby the files created by these users have to have the permission bits as 664. Obviously, I changed the UMASK value for these users from 022 to 02. But the files are still getting created with 644 as the permission.
I tried restarting the application as I read that a relogin is required for the UMASK change to take effect. Even that hasn't helped.
On my Ubuntu 11.04x64 server, I have service accounts running which do not log in and do not have home directories. These service accounts are responsible for running processes which are invoked as services.When these services created new files, I need them to be created with the permissions 664 (UMASK 002).I edited the /etc/profile umask setting to reflect this. I see that now my user account creates files which reflect this new umask setting, but the service accounts do not when I manually created files using their accounts (sudo -u serviceaccount touch newfile).
I am trying to set the umask for a process(orkaudio) which is running as the root user.This program creates dir and files and I need the umask to be 022. I have edited my /etc/bashrc -- and when i type in umask i get 0022 --- Not sure how to go about getting this resolved...
I have ext3 partition mounted on /mnt/shared/ as follows
Permissions above are of the actual mounted fs.
Goal is to have all files created on the fs 1) to belong to group 'users' 2) to have this groups permissions set to rw (rwx for directories) so that all users who belong to group 'users' have full read/write access to data and everyone else to have only read access.
Now because of setgid bit (s) in group permissions every file created has group 'users' and additionally setgid bit is set for directories. Because every users umask by default (on my system) is set to 0022 all created files will have permissions 644 for ordinary files and 755 for directories.
Net result of above means that users A and B who both belong to group 'users' won't be able to modify files created by the other.
So how can I make files created on the fs to be created always with umask 0002 WITHOUT changing default umask for users that is used elsewhere (like in their home directory) ?
I'm struggling to understand an aspect of mounting and mountpoints with /etc/fstab. There is a large number of sites and threads that make recommendations using things like uid, gid, umask, and other options. These methods, however, which I've used, are file-system specific, useful only for filesystems such as (V)FAT and NTFS that allow them.My current situation is that I am mounting partition /dev/sdb5 in, let's call it /media/myMount. My goals:Mount this partition automatically upon boot using /etc/fstab...The partition should be fully accessible only to a specific user or group.What I've done is create the mount point in /media:
If user michapma were to carry out the mount, I believe it would work; however, I want the mount to happen automatically during boot. So, how can I achieve my user (or group) permission goals for this and any other such partitions using fstab?The manpage for mount has been helpful, but after reading many tutorials and forum threads, the only way I know how to do it is to have the user do the mounting or rely on the file-system specific options.
I have about 5 users for our desktop computer, 1 adult, 3 kids and me (I don't count as an adult ).
There are some settings I want to have each of the environments default to, where they can then change them as they wish on their own.
Instead of setting them one-at-a-time, is there a way to modify the settings on the template of what goes into a user's /home directory when they are created?
Examples: Set it so when I add a person to the system theirdefault browser is set to Firefox starting home page is to our local server Open/Libre Office defaults to MS Office formats And others, less important ones like their pictures are placed in a centralized directory, not their own ~/Pictures.
After this initial setting, they are able to change any and all of these settings on their own, but to have these as default helps me set up their environments to get them started.
Sorry if this question has been asked before, but I am trying to figure out how to set a custom default background so that any user that logs onto the machine (via our LDAP server) will see the background that I have set to be default.
I am extremely new to Ubuntu (mainly a Windows person) but am trying to create this environment to give our students an option to boot either into Windows or Ubuntu.
I need to set up quotas so each user has a limit of 20GB (soft could be 15GB) on their homes.Is there a way to set up a default quota for all the users, or do i have to do this for the 345982374058 users in my system manually?would group quotas help? (i dont understand much of these type of quota)
I'm looking to customize the environment for new users by changing the items in the GNOME menu, change the panel layout, add some shortcuts, and do a few other things. I looked in /etc/skel and there doesn't seem to be anything GNOME related in there; I also tried to put .gconf, .gconfd and .gnome2 from my home directory into /etc/skel and that didn't do what I wanted.
I came across this script a while back that i found. What i want to do is edit the script to create a default web page in /var/www/html a new user is added through the script.What the script does now is adds a user and sets a password for the user. What possible way (either through a combination of python or c or some other language) could i add to the shell script to do this? I've tried just dointhe command to touch index.html /var/www/html but it puts it on the desktop. Here's the script....
Code: #!/bin/bash # Script to add a user to Linux system
I've got a small issue that when a Windows user creates a new folder through Windows Explorer (from the menu or by right clicking) the new folder is only accessible to that particular user. Example: user SABKAR (member of the HR group) creates a new folder called MarcTestMenu in a shared Samba directory through Windows Explorer:
At this point user MORAMY cannot copy a file or open the directory MarcTestMenu. MORAMY gets a 'not accessible' error message in Windows. If I su to the Samba box and issue this command:
how I can get the correct default permissions when users create directories through Windows?