“Symbolic link not allowed or link target not accessible” / Apache on CentOS 6
I’ve got a brand new CentOS 6 installation, which has a symlink in the document root to my development files:
I’ve got a brand new CentOS 6 installation, which has a symlink in the document root to my development files:
The /etc/sudoers file lists which users can do what with the sudo command The root user creates and modifies the /etc/sudoers file. This concept is difficult for me to understand. If all users having sudo privilage belong to sudoers group, then all of them can become root by giving the sudo su command. Then who … Read more
I have device file that appears in /dev when a specific board is plugged in. The read and write operations to it work just fine, but in order to open the device file the program needs to be executed with root priveledges. Is there any way I can all a non-root user to open this one specific device file without having to use sudo?
I can’t manage to set x bit to created file.
How is it possible I am not able to read the AS file below?
What does the letter S mean below? The file in question is a folder.
I made a backup to an NTFS drive, and well, this backup really proved necessary. However, the NTFS drive messed up permissions. I’d like to restore them to normal w/o manually fixing each and every file.
Is there a way to back up and restore file ownership and permissions (the things that can be changed with chown and chmod)?
After upgrading to a new release version, my bash scripts start spitting errors:
When I run chmod +w filename it doesn’t give write permission to other, it just gives write permission to user and group.