Reshare Samba Mount?

We have a +1TB server which is running Linux (Gentoo I think) and want to use it as a sharepoint for our clients.
It is stored away from our OS X Server, firewalled and accessible only by the server (it also stores backups) and admins.

The OS X server can mount the Linux share via Samba, and has full permissions. I want to be able to "reshare" this volume from our OS X Server to the clients, so that it mounts when users login.

Yes, we could simply have the clients mount it when they login, but we want to use ACLs to prevent users from deleting and modifying backups - they should only be able to write backups or copy their backups back to the client.

e.g. Backup Server (Linux) > OS X Server (full permissions) > Clients (restricted permissions)

Evidently it isnt possible to share a network volume in WGM, so I was wandering if it would be possible to mount the backup server as a local volume and hence share it this way? We need some way of restricting client access. Unrestricted access has caused many headaches in the past.

I don't quite know if ACL's are the way to do this, or if it is even possible.

Suggestions much appreciated!! Cheers


james

12" iBook G4 : 1.2GHZ/768MB/60GB/APX/Combo, Mac OS X (10.4.6), 1G iPod 5GB, 5G iPod 30GB (white); PowerMac G4 DP Server (Tiger)

Posted on May 9, 2006 4:59 AM

Reply
5 replies

May 12, 2006 12:44 AM in response to jamesd

OK, this should help - you need to reshare the folder using NFS instead of SMB/CIFS.

First off, re-sharing a volume that uses the smb filesystem is not possible due to the way permissions are calculated for that volume. Regardless of the local filesystem of the volume that houses the share point on your Linux server (ext3 or whatever), that share point's filesystem as it appears to all clients, including your Mac OS X Server computer when it connects as a client, is the smb filesystem. Since that's a network filesystem already, some types of information cannot be "appended" to it. AFP and SMB/CIFS filesystems, when mounted via Go/Connect to Server (or mount_smbfs) will use a set of masked POSIX permissions. (This means that, if you're logged into the server as a local admin - locadmin, for example - and you mount the SMB share point as Sally, then locadmin is the owner of the mount point and its enclosed files. The currently-authenticated user is granted the permissions assigned to the user account used to connect. Hence, permissions masking. This happens in every instance when mounting a volume via SMB/CIFS. It happens when connecting to an AFP share point except when the client is bound to a shared directory system, where the user name authenticated at the login window matches the account used to connect to the share point.)

One of the reasons that you can reshare an NFS volume is that you can tell the other server - your Linux box - to map the connection coming from your Mac OS X Server box to a user with read & write permissions to the NFS export (share point), usually the owner. In this way, any commands sent by Mac OS X are issued as the owner of the NFS export, according to the Linux system's point of view. The main difference here is that, since the mapping is defined on the Linux box's system, Mac OS X does not employ its own permissions masking.

Even so, you may or may not be able to enable ACLs on the NFS mount. You can try issuing sudo fsaclctl -e -a to enable ACLs on all volumes that support them. If you define a local folder as the mount point and use mount_nfs to mount the NFS export from your Linux box, you may be able to use ACLs on it.

Consult your Linux box's directions for creating an NFS export. Most Linux and UNIX systems support standard NFS, so the challenge would be finding directions for your particular system. Since NFS defines permission masking on the server side, there's no "name/password" authentication going on when you connect on your Mac OS X Server system. Instead, when defining the NFS export, you'll tell the Linux system from which IP address the server will be connecting and what kind of mapping to use ("all users to root" would be necessary if you want the Mac OS X Server box to control access). For security reasons, it would be best to isolate the network that connects your Linux box and Mac OS X Server system. Consider using a second Ethernet port in your Mac OS X Server system with a unique private addressing scheme, and construct a two-computer network consisting of just the two servers.

--Gerrit

Jun 12, 2006 3:24 AM in response to Gerrit DeWitt

Hi Gerrit,

Apologies for the late reply but I just wanted to thank you for your hugely thorough response. Very enlightening!

It proved a tad too difficult to set up as you described, so we set up an 'interim' backup volume on the main server. Users backup their files to the OS X Server (shared with ACL's) and then each night these files are moved down to our Linux Server. It works, just not as neatly as we had hoped.

When I have some more time I will try and share the volume using NFS.

Thanks again.


james

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Reshare Samba Mount?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.