lsaranto

I have a habit of deleting just the downloaded files after I have reviewed them, and leaving the torrent file to the torrent software. uTorrent (Windows) marked the files with error permanently. ruTorrent seems to mark them too, but if ruTorrent is restarted, it forgets the error state. It then looks like the torrent has never been downloaded. This leads to unnecessary redownloads. Is there a workaround?

In my case, I needed to limit access to a directory that is a few levels down from the share top. Yes I could have moved it to its own share, but that is not its logical place. I tried to use ACL but didn't have enough skillz. What I ended up doing, was that I made my user the owner of the directory with +rwx rights, I gave +w rights to group as a certain program needs to be able to write to that directory, and -rwx to other. This isn't perfect. I think, technically, the blocked user is able to write and delete files from the directory. But in my case it's enough to keep out family members who have never seen Linux.

Have you tried following the guides listed at the end of this page https://flows.nodered.org/node/node-red-contrib-alexa-remote2 ? In one of those guides it says: File Path is the place where you should type something/anything, meaningful to you like “authFile”. The plugin will create a file with that name and inside the file, it will store your encrypted Amazon credentials. This is needed because otherwise it will ask you to re-login every time you re-deploy your Node-RED flow. So you should only put a filename in it, not a full path. Maybe.

How familiar are you with Linux file and directory structure? /mnt/user/appdata/nodered is the host directory. ./ is the directory itself. ../ is the parent directory (in this case /mnt/user/appdata). If you want to look things from the container's point of view, you need to load the container and then start a shell in it with docker command (docker <somethingsomething>). Sorry, I'm not that familiar with the docker command. In general, I believe, all files under appdata should belong to nobody:users (99:100). Have you tried that? Looking at my own appdata/nodered files: all directories and the last 3 files are owned by nobody:users, The rest are owned by 1000:1000. Except for the cookie.txt which I don't have.

I think you need to use the container directory. /mnt/user/appdata/nodered is the host directory that the container directory is mapped to. You can see the container directory from the docker settings. It's probably /data .

I have a zigbee switch that sends out a magic packet with the VM's mac address.

So, there¨s a docker image called MQTT and Mosquitto. What's the difference and which one I should be using?

Well, that would have been easy... but no. Beep works in Unraid console. But in the container I get "beep: can't open console". I remembered that I have cheap unused USB speakers somewhere. But is that also a no because no drivers?

I need to make a pc speaker beep or other noise from inside a docker container (Node-red). How would I do that? A cheap external speaker or something is a possibility also.

I want to restrict access from a user to certain sub-directories in a share. My share is called "share1" and in that share I have directories labelled dir1, dir2, dir3. I have added users called "user1" and "user2" to Unraid. "user1" and "user2" are also Win10 usernames. I want everyone including "user2" to have access to "share1", but only "user1" should have access to dir3. I tried to google it and I tried setfacl, but it's not working.

I'd have use for this.

From the guide in the first post:

Thanks! I just had the same error. I had run a script with too few double quotes. In the end I had a share with a backslash in its name. Removed the share and everything is fine.

I have build my first Unraid system. I have a monitor connected to the graphics card, because I use it also with a W10 VM. When not running the VM, I'd prefer the monitor to sleep when it sits at the login prompt. But it won't. The screen goes black, but when the room is dark you can see the backlight. Also the monitor's LED indicator stays green. And it's wasting electricity. I've searched the forum and they offer a couple of solutions. I've tried them, but get only error messages back. root@Tower: ~# setterm --powersave powerdown --powerdown 1 setterm: cannot (un)set powersave mode: Inappropriate ioctl for device root@Tower: ~# vbetool dpms off Failed to initialise LRMI (Linux Real-Mode Interface). My Linux skills are not good enough to do anything else on my own. If it's just not possible to get the monitor to sleep, then possibly even more useful thing for me would be to put the monitor power switch to good use. So maybe it is possible to detect when the monitor is turned on and then launch the VM. Either by detecting the monitor itself or the USB device(s) connected to the monitor's USB hub. unRAID: 6.7.2 (Trial) Motherboard: Supermicro X10SRA Processor: Intel Xeon E5-1650 v4 @ 3.60GHz Memory: 4 x 8 GB ECC Graphics card: 2x Asus Radeon HD7750 1 GB Monitor: Lenovo ThinkVision L220x (DVI) & Sony KD-43XF8599 (HDMI)

I get the same error. I followed the setup guide on Reddit. I've added the conf file. The docker keeps recreating a directory called telegraf.conf.

Well then. I guess I'll have to test the HD 7750s before I buy new ones. I don't have the other hardware for the server yet, so it will take a while. I'll post an update.

Do you experience the Radeon reset bug?

According to Asus's FAQ and TechPowerUp.com BIOS collection the HD 7750s that I have don't support UEFI. I was hoping to be able to passthrough them to a W10 VMs. I should have mentioned that in the opening post. I've done a lot of reading since posting the question. My current understanding is that it can't be done with W10 without UEFI support. Also, it seems some Linux distros are out.

Can I use a Radeon HD 7700 gfx card for passthrough? All of the examples I've seen are using Geforces or newer Radeons.