The executable files that gcc creates have execution permissions
which are different than the permissions that the source file has.
How does gcc set these permissions ?
I am trying to make changes to my website over ftp but when I save any files it changes the permissions and owner to my username. I can edit files in the same folder trough samba without changing the permissions. I really don't understand how the permissions for the /var/www folder work and I'm pulling my hair out trying to get it to work.
I'm writing a bash script that does a little house-cleaning for me (clearing the log files from any Rails projects in the current directory). I'm making it executable, and I'm not sure what best practice dictates as far as setting the "group" and "others" file permissions.
Changing permissions in a script after installing certain apps (Linux and OSX), I found the following very confusing.
Creating an ".app" in OSX requires placing a directory with a number of files (application, resources, libraries) in the /Aplications directory, with root permissions. The app could be pulled from a CD or network, which means that its permissions are really not what I need.
I have an ftp process that is connecting to a Solaris server and pushing files into a directory. The default file permissions are rw-r--r-- . I want the file permissions to be rw-rw-r--. How can I configure the directory so any file created there will have the permissions rw-rw-r-- ?
*Note the permissions on the directory are drwxrwxr-x
Is there a way to invoke unzip (from Info-ZIP) without having it restore the permissions stored in the zip file? The zip files I'm restoring are enormous, so going back over the contents with something like "chmod -R" will take a while. I do not control the source of the archives, so my only choice is to handle the permissions on extraction.
Is there a way to invoke unzip (from Info-ZIP) on a Linux system without having it restore the permissions stored in the zip file? The zip files I'm restoring are enormous, so going back over the contents with something like "chmod -R" will take a while. I do not control the source of the archives, so my only choice is to handle the permissions on extraction.
I just can't change any file permissions even when I am logged in as root.
I tried changing the permissions from both terminal and i got no errors but the permissions remain the same. And when i try to change by right clicking and selecting permissions tab in properties they instantly revert back.
Am using Ubuntu 13.10
As I've found out, when using umask, the highest permissions you can give to files are 666.
Which is done by umask 0000. That's because of the default file creation permissions, which appear to be 666 on every system that I know.
I know for files we need executable rights to show their contents.
But why do we limit the default file creation permissions on 666?