xieve

I wrote a daemon script that watches a share for changes via inotifywait, and I would like to suggest a few features that would really help in this usecase: a config option to prevent two instances of a script running in parallel Sending SIGTERM instead of SIGKILL when you click "Abort" (or offer this as a config option, or provide two buttons) because I want a simpler way to shut down the daemon. Currently, I use htop, I've thought about implementing sth with a pidfile, but it gets complicated fast. (Edit: SIGKILL also prevents the use of flock to achieve that only one instance can run at a time because the lockfile is not released.) (Providing an option to) terminate running processes that have arrayStarted=true when the array is stopped (currently, I have to do this manually, because inotifywait blocks the unmounting).

You can paste this in [server address]/Settings/SMB, which will put it in the exact same file.

I also have this problem with Surfshark. Edit: I fixed it I googled for a while and figured out that this was an MTU issue. My rough understanding (correct me if I'm wrong) is that the VPN provider limits the package size to below 1420 bytes, which seems to be a standard value for Wireguard. This is not correctly detected by MTU discovery and thus if we try to send larger packets (which HTTPS does) they are simply dropped. So first, I figured out what the actual MTU should be by using differently sized ping like this: ping -I wg0 -c 4 -M do -s [SIZE] 1.1.1.1 SIZE being the packet size to be tested minus 28 bytes, which seems to be the ping overhead. After a bit of trial and error, I figured out that Surfshark has an MTU of 1370 (meaning the max size of a ping was 1342 bytes). I set this in the VPN settings (you have to enable the "advanced view" on the upper right) and tested it, but it still wasn't working. (It might work for you at this point.) This is where MSS (maximum segment size) clamping comes in. I don't know exactly how it works, but it forces the packet size to always be under a specified limit, which is exactly what we need. I tested it by executing this in the host console: iptables -t mangle -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu And it worked! Now all I needed to do was persist this change. I installed the User Scripts addon and created the script attached to this post. All you have to do is extract the archive to /boot/config/plugins/user.scripts/scripts, then go to Settings → User Scripts and set the schedule to "At First Array Start Only". clamp-mss-to-pmtu.zip

There's a docker container for the Urbackup client. I've made a template and attached it (drop into /boot/config/plugins/dockerMan/templates-user/). xieve-urbackup-client.xml

I have the same problem. ls shows this folder to be owned by 967:967. If I chown it to nobody:users on the host, I get this instead: 2023-11-21 11:04:50,089 DEBG 'urbackup' stdout output: ERROR: Image mounting failed: Loading FUSE kernel module... modprobe: FATAL: Module fuse not found in directory /lib/modules/6.1.49-Unraid Starting VHD background process... Waiting for background process to become available... Timeout while waiting for background process. Please see logfile (/var/log/urbackup-fuse.log) for error details. UrBackup mount process returned non-zero return code I've also tried making the container privileged, adding the /dev/fuse device and loading the fuse module on the host system. The issues stayed exactly the same.