Page 1 of 1
Forum

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!


Forums
Software
Tweaking4All Applic...
ConnectMeNow
How to change umask...
 
Share:
Notifications
Clear all

How to change umask of files in mount?

 
ConnectMeNow
Last Post by Hans 2 weeks ago
2 Posts
2 Users
0 Reactions
73 Views
RSS
 udance4ever
(@udance4ever)
Active Member
Joined: 3 weeks ago
Posts: 3
Topic starter November 16, 2024 7:57 PM  

I poked around the mount man page and I don't see an option to change the umask on macOS.  Is this possible?

Right now the files in my mount are only readable by the user that has the ConnectMeNow configured to automount the share.

Is there a way to change the umask so the mount is also world readable and group writable?

This topic was modified 3 weeks ago by udance4ever

   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2805
November 21, 2024 9:30 AM  

Apologies for the late response ... (got some family issues to deal with)

I haven;t had to deal with this in a very long time, so maybe these thoughts can get you started:

  1. As far as I recall, this depends on the server/host config of the share and the protocol you're using (I assume SMB?).
  2. I have read about children inheriting the permissions from the parent, so if a directory has the proper permissions (chmod, maybe on server and client) then their children will as well.
  3. Seems "mount" (mount_smbfs) has the "-d" and "-f" option, but I have to say that I never used these (the command line option, under Advanced options in ConnectMeNow allow you to add command line options).

In my experience (which may not be the best 😉 ): I always ended up fixing the problem on my NAS/Server. Set the proper rights there for the user(s).


   
ReplyQuote
Forum Jump:
  Previous Topic
Share: