Having a Application Use option when setting up a share would be grate.
What?
SMB is grate, but if you want the network drive to work with applications using it for there data, you need to config samba so it can use SMB features like Hardlinks, Symlinks, Space pre-allocation, and partial file writes. You basically need SMB to more closely mimic a file System so programs don't get tripped up with an IO.Write error when it try's to do something SMB has not been configured to do.
You also need to lax the security because on windows, user, admin and system are all in them selves classed as different users. So if you set up your share on a user account, and the app is ran as admin, you end up with the app not being able to see the share, or will write new files as nobody, Creating incoherency between running the application as a user and as administrator. The more lax security and promiscuous permissions however means you do not necessarily want your data on the same share, or need to rely on client restrictions instead so only one IP can see and use it.
Having a tick box stating that a share is intended for application data would be grate. It should then force you to enter the address of the PC that can access that share, and set up the more promiscuous SMB settings such as allow wide links, Unix extensions, Nobody user and group mapping, the client restriction to that one ip address and various other samba configurations for samba and that share, fully opening up SMB's Capabilities.
Why would I want this?
Glad you asked. there are Two common scenarios where this is very useful.
1. NAS steam library.
2. NAS backup location.
One common use case of setting up samba in this way Is to set up a share as a steam library. When fully opened up, Steam will, quite happily, use a samba share as a Steam library and works mostly without hiccup. Another reason you may want to do this is for backup applications. Backup software loves symbolic links and hard links, and utilise them heavily to cut down on back up size and structure the backup data to be accessible from one easily clickable folder. Backup software also likes the partial file read and write support so it only has to update what's changed.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Ad-Man-Gamer
Having a Application Use option when setting up a share would be grate.
What?
SMB is grate, but if you want the network drive to work with applications using it for there data, you need to config samba so it can use SMB features like Hardlinks, Symlinks, Space pre-allocation, and partial file writes. You basically need SMB to more closely mimic a file System so programs don't get tripped up with an IO.Write error when it try's to do something SMB has not been configured to do.
You also need to lax the security because on windows, user, admin and system are all in them selves classed as different users. So if you set up your share on a user account, and the app is ran as admin, you end up with the app not being able to see the share, or will write new files as nobody, Creating incoherency between running the application as a user and as administrator. The more lax security and promiscuous permissions however means you do not necessarily want your data on the same share, or need to rely on client restrictions instead so only one IP can see and use it.
Having a tick box stating that a share is intended for application data would be grate. It should then force you to enter the address of the PC that can access that share, and set up the more promiscuous SMB settings such as allow wide links, Unix extensions, Nobody user and group mapping, the client restriction to that one ip address and various other samba configurations for samba and that share, fully opening up SMB's Capabilities.
Why would I want this?
Glad you asked. there are Two common scenarios where this is very useful.
1. NAS steam library.
2. NAS backup location.
One common use case of setting up samba in this way Is to set up a share as a steam library. When fully opened up, Steam will, quite happily, use a samba share as a Steam library and works mostly without hiccup. Another reason you may want to do this is for backup applications. Backup software loves symbolic links and hard links, and utilise them heavily to cut down on back up size and structure the backup data to be accessible from one easily clickable folder. Backup software also likes the partial file read and write support so it only has to update what's changed.
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.