Leaderboard

Popular Content

Showing content with the highest reputation on 09/12/19 in all areas

  1. OH, things just keep getting better and better. Can you see them in the file explorers on the MacBook and Windows? One thing I just notice while ls sorts files alphabetically, CAPS come before small letters. So Files letters data files sort this way Files data files letters EDIT: Be careful with this example. Windows will only find one of those two with the same same base (Files and files). The other one will be invisible. Folks have 'lost' whole groups of files by putting them into a directory on an Unraid system with two directories that differ in name only the first letter being capitalized!
    1 point
  2. Try this: grep '^group_name_here:' /etc/group This is new ground for me as well as you. As I said, "Google is your friend" and I must admit that I do not not the in-and-outs of exactly how things are handled. I assume that your conclusion is correct but I have no firm proof of that truly being the case. I was never involved with a Windows Server setup that used AD. (I do seem to recall seeing some posts on this forum about folks not having great experiences linking Unraid to it.) I actually retired before 'Windows for Workgroups' was introduced but I did help administer a UNIX server that provided file serving for a number of DOS computers that were connected by means of AT&T StarLan. As I recall, we also had a Laser printer (Do even ask the cost of this device) connected to this network. The entire network was less than twenty devices
    1 point
  3. Another thought. Did you map these shares to your PC as a drive? Did you rework the WIN10 permissions on this mapped drive? The reason for these questions is simple. You should not have to do anything on the WIN10 end for any additional security on any Secure or Private Unraid SMB share. All of the protection is being provided on the server by the Unraid SMB system. (IF the Unraid SMB did not do this, the file would be exposed to any (say) Linux computer!) The system sharing storing the file must provide all of the file security. Thus if you share one of your local hard drives on your WIN10 system, you will have to lock down the files from that computer. I am not sure quite what the Unraid SMB system is going to do if you are implementing file access restrictions on the WIN10 end, It could cause those ACL extensions to be applied!
    1 point
  4. Did a bit more research. Did you notice the + sign on the -rw-rw-rw-+ string of permissions for all your files and directories. Apparently that means that there are extended permissions called ACLs. (Google is your friend in these cases.) There is a command--- called getfacl ----- that will list these. So try this command: getfacl /mnt/user0/MWPBDocs/Logo/Computer\ BG.jpg and let's see what it tells us.
    1 point
  5. Try this command first: chmod 777 /mnt/user0/MWPBDocs/Logo/Computer\ BG.jpg Then check if the other user has access to the file. You can see what this command did with this one (again): ls -al /mnt/user0/MWPBDocs/Logo
    1 point
  6. You have to edit the values in the rtorrent.rc file in your appdata/rutorrent/rtorrent folder
    1 point
  7. Use the Up-arrow key to recall the last command. The arrow keys are very useful in the Terminal window. play with them a bit...
    1 point
  8. Bingo! Looks like NoMachine added its own audio adapter and now I get sound! Thanks Bastl!!!
    1 point
  9. OK, open the terminal (it is the >- symbol on the Toolbar). type the following ls -al /mnt/user0 That will get you something like this: total 4 drwxrwxrwx 1 nobody users 75 Sep 8 02:30 ./ drwxr-xr-x 9 root root 180 Aug 6 10:58 ../ drwxrwxrwx 1 nobody users 305 Sep 1 18:20 Backup/ drwxrwxrwx 1 nobody users 273 Nov 6 2017 CommunityApplicationsAppdataBackup/ drwxrwxrwx 1 nobody users 4096 Aug 27 19:01 Media/ These are the Shares on this server. Now pick one of the shares that contains a file that has the problem. I am going to proceed using the Share 'Media'. (Note capitalization is IMPORTANT with Linux!!!) ls -al /mnt/user0/Media This gives an output like so: total 8462508 drwxrwxrwx 1 nobody users 4096 Aug 27 19:01 ./ drwxrwxrwx 1 nobody users 75 Sep 8 02:30 ../ -rw-rw-rw- 1 nobody users 7726504 May 24 2017 100-Magic_Act.mp4 -rw-rw-rw- 1 nobody users 169788268 Mar 2 2013 107D_OutdoorCupboard.mp4 You will, of course, have will to pick a path down to a directory which has a file with the permission problem. When you find one, left click at the beginning of it and 'sweep' the entire line. Now right click on it and copy it. Paste into a reply. Be sure to format it as 'Code' --- the </> symbol on the Toolbar --- as this will keeping everything lined up neatly.
    1 point
  10. Have you run the Docker Safe New Permissions script (it is part of the Fix Common Problems plugin)? Tools >>> Docker Safe New Permissions Does this fix the problem temporarily? Do you know how to use the Linux (or UNIX) command line? The reason being, it could be problem with the owner/permission settings and it is necessary to find out how the underlying Linux system is handling those. We can walk you through the procedure but it would be easier knowing where you are. (You only need a very slight knowledge to get the information that is needed.) But the amount of instruction necessary from no knowledge to some knowledge is considerable!
    1 point
  11. Looks like a problem with the Marvell controller, don't use those 2 ports.
    1 point
  12. Today's update to CA Auto Update will automatically apply the fix for this issue on affected systems (Whether or not the plugin is even enabled). You will though have to check for updates manually once to clear out the old update available status. If you are running @ljm42's patch script, you can safely remove it, as the Auto Update will not install the patch once 6.8+ is released.
    1 point
  13. Once you wrap your head around how all the array and cache disks interact to form the user shares, you can safely move files from disk to disk to get your least used files consolidated onto drives by themselves. It's not super complicated, but until you understand it, don't start playing around with the individual disks, as you can cause anything from hiding files from yourself to outright irretrievable data loss. This thread is one place to start learning if you wish. https://forums.unraid.net/topic/42152-disk-vs-user-share/
    1 point
  14. For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp
    1 point