Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are a web design company who develop off files stored on a osx leopard server. The issue is that when a developer creates files using textmate in a folder for a new website, when another developer using dreamweaver goes to open and edit these files they are readonly and visa versa.

The only way it seems to get round this is to chmod the files before opening them to 777. Unfortunately when these are uploaded the permissions are maintained, creating potential security risks for our web applications.

Any ideas on how to stop this file locking occuring? Note the files are not already open in either application.

share|improve this question
up vote 0 down vote accepted

Make sure all your developers are in the same group, so you can set files to 664 (775 for dirs). This is safer than chmodding to 666 or 777 as long as the group the webserver is running doesn't have the same groupid.

share|improve this answer
we realised one developer (who first started work on the site) was connecting to the mount/server using guest rather the correct login, thus creating all these permission issues. This is now resolved thank you. – Alex Crooks Jul 6 '10 at 8:13

You'll need to change your umask. I'm not sure if it affects network mounts. Edit the file: /etc/launchd-user.conf add a single line: umask 002

if it doesn't work, how are the clients mounting the share (AFP, SMB, NFS?) you could update the configs of the sharing methods to force specific permissions being written. Also a cron job to add group write permissions might do it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.