![]() ![]()
Should users generally access and store their own stuff with network paths such as \\mysyn\homes\susan\documents or \\mysyn\homes\fred\music? With a user login you will only see your personal /home/username folder, not /homes/. Use that login only for NAS admin duties, not for storing your personal files, streaming, downloading, etc. You're apparently logged in as an administrator. I no longer remember whether I created this or if it was automatically created for me. It appears that I have a share "homes" that currently isn't granted to most users. ![]() When I browse the network from a client workstation I can currently see "home" and "homes" but cannot drill down into them to see their contents.Do I want to enable "Advanced Share Permissions" on the share? What does this actually do?.I assume I don't want to start going down the track where I create top-level shares like \\mysyn\fred or \\mysyn\susan.Will synology user permissions protect the individual user subfolders under home on a per-user basis even if all users have access to \\mysn\homes?.To make this happen should i grant read/write to all of these users on the common share "home"?.should users generally access and store their own stuff with network paths such as \\mysyn\homes\susan\documents or \\mysyn\homes\fred\music?.It appears that I have a share "homes" that currently isn't granted to most users. Synology homes folder default permissions software#XnViewMP, CANNOT save file into it.I must be missing something here, and want to make sure that I'm proceeding in such a direction where I won't be fighting Synology's software repeatedly.Īre we intended to have user home directories or subdirectories as network shares that can be mapped via SMB, AFP, etc.? > Although other applications can see this shared folder, but they, e.g. > However, many other applications, such as Firefox, Google Chrome, NotepadQQ, XnViewMP, CANNOT see the mounted folder directly, and can only see it by browsing into the folder "/run/user/1001/gvfs/smb-share:server=hnas3.local,share=folder1" > I CAN delete files under synology shared folder using Nautilus File Explorer (5) If I mount synology shared folder thru Nautilus File Manager (it seems that it use "gvfs" to do the mounting), e.g folder1, (4) Using Nautilus File Manager, I CAN delete file of home folder of a synology user, e.g. folder1, using the "rm" command, whether or not I am a root user or NOT but failed to do so in GUI Nautilus File Manager. (3) In terminal mode, I CAN delete files in shared folders, e.g. (2) but for the home directory of the Synology user "user1", it's normal "folder1", "folder2", & "folder3", I can create or paste new files, change file names, but CANNOT delete any one of them (1) for files under the shared folders, e.g. However, it's weired that using ZorinOS's default file manager "Nautilus": Synology homes folder default permissions Pc#I have successfully auto-mounted shared folders to my Client PC running ZorinOS12.1 thru "NFS" according to this URL: Synology homes folder default permissions update## NAS Server: Synology Diskstation DS716+II, with DSM 6.1.3-15152 Update 1 # Client PC: ZorinOS12.1 ( ), AsRock J3160 mini-ITX, 8GB Ram, 120GB-SSD ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |