We have various of machines here with all sorts of hardware and Operating Systems, most of them do regular tasks with bash that an agent executes.
However it came to my attention that some Solaris machines we own do not have stat util, and adding it would be a problem that might take time (ironic)
Meanwhile I was trying to imitate one sisyphean task which stat did in a magnificent way:
return th
Sigh...:confused:
I've read multiple times about file permissions and Samba sharing. I am still confused. It seems that what I have learned so far is that what a user can do in a Samba share is affected by both Linux and Samba permission settings.
The /etc/crontab file has the permissions:
-rw-r--r--
I understand that this file is for system cron jobs and other users should not have permission to modify it. The current permissions allows all users read access to the file, enabling them to view the contents.
Is it necessary for all users to be able read /etc/crontab?
I encounter a strange problem on a unix/linux machine:
I'm member of a group, let's call it group A and a certain file (which has a different owner) belongs to group A as well. The permissions of that file are
-rw-rw----
so I'd expect I should be able to open that file, but I am not: I'll get the "Permission denied" error message when I try to look at the file's content (using cat).
Hello,
Please I need help with "ipa permission-add" command.
I am implementing file server connected to freeipa and following problem showed up:
I am using bind user, who read end user attributes, but sambaNTPassword is protected for reading.
I tried "ipa permission-add" command, permissions was add, but does not work.
3-digit:
644
ugo (user group other)
4-digit:
0644
?ugo (??? user group other)
What is the first octal digit for in 4-digit octal Unix file permission notation?
I have a file which was saved to a CIFS share from Outlook. The file permissions are 777, so I should be able to read the file from the Linux host the file goes to. However when I try, I get file permission errors (unable to read the file). If I have the root user change the permissions (say from 777 to 775), I am then able to read the file as expected.
I always wondered why rsync tries to transfer a file to a remote location where it has read/execute permissions for the target dir, but no write permissions to create the actual destination file.
I have a shared EXT4 drive with 777 permissions for all users to use.
Problem is :
When a user creates a new folder / file, it gets 644.
I guess that is because of the umask for that user.
Now, I want to have all the new content with 777.
Email this page
