mdajr

Bummer. I quite liked it. Anyone know of a good replacement?

Can someone post their $PATH variable? Mine has a dot "." in the beginning which 1. Is generally not good security and 2. Is breaking my find -execdir command. Trying to figure out if this is an Unraid thing or if I screwed it up somehow. From SSH run echo $PATH Here's mine: .:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin

Bump. Same here. I'm a software engineer so I'm fully aware of how timelines shift so I really hate to pester the devs. Last we've heard was a 6.9RC1 coming "a few days after" 6.8 was released but that was back in December. I'm sitting on 6.8RC7 because I need the 5.0 kernel but I'm missing out on the critical security patches (which I assume is why 6.9 got delayed).

I like how functional the GUI is. Makes it super easy to configure and use. I’d love to see integrated Nvidia support for easier access to the gpus in docker.

Appreciate the help. Looks like the minimum free setting was set to 2MB. Changed that to 10GB and got the mover going like you said. All is good. Thanks!

Hi all. Running 6.6.6 and have some confusion about the cache disk. I created a new share and set use cache to 'Yes'. I then started moving a large number of files (more than the size of the disk) from Windows 10 to the share in one drag and drop. Eventually I reached a point where Windows halted the move and reported that the disk was full, and asked if I wanted to try again. My questions are: 1. With use cache being set to Yes, I though that once it fills up it will automatically start writing to disk instead. In this case the cache filled completely (I guess it was in the middle of a file) and Windows refused to continue to write, even when I clicked Try Again. Did I misunderstand / misconfigure something? 2. The only way to get the file move going again was to change the Use Cache setting to NO. Windows then proceeded to move the files as normal. I invoked the mover, however after running (for only a minute really.... way too fast it seems) it only lists 3GB free, which I'm assuming means that it moved nothing off the cache. Are the files from the beginning of the move now orphaned on the disk? Do I need to manually move these to the share in /mnt/user ? Will it find the files again if I turn Use Cache back to on? Thanks in advance!