Tag Info

New answers tagged

1

I don't believe it is possible to make the behavior you desire the default / general behavior. Look here for details regarding "base permissions". For files the base permission is 666 or rw-rw-rw while for directories it is 777 or rwxrwxrwx. umask may further restrict base permissions, but cannot grant additional access. In other words, umask cannot be used ...


1

Talked to the infrastructure people, and the answer is that there are extended ACLs in place that act differently based on location, and that they were erroneously set.


0

The only time I have seen this kind of scenario is when the NFS share is exported from a Windows server running NFS for Windows services. The POSIX attributes demanded by the Unix/Linux world aren't mapped cleanly onto the NTFS attributes and the result is that permissions display one thing and (sometimes) act as another. In our particular situation we ...


-1

If the sticky bit chmod +s is set on the folder, the umask is overridden with the attributes of the folder owner. that is why you may be seeing inconsistent results between folders.


2

I would use the install tool to copy from NTFS. install -m644 file1 ... fileN destination_directory


3

You could use a script for your own user-defined cp command that checks file extensions and uses chmod appropriately... You could do something simple like: (using install rather than cp chmod as per @fd0. That's smarter anyway.) #!/bin/bash args=("$@") dest="${args[@]:(-1)}" unset args[${#args[@]}-1] if [ ! -d "$dest" ]; then echo "Please specify a ...



Top 50 recent answers are included