deleted by creator
deleted by creator
my solution to this is to only deal with the UPS in proxmox. it shuts down everything if the battery goes below a certain level.
I think you can configure nut to run a few scripts when something changes around the UPS. you could have a script that sends an alert through ntfy, and/or the web services that you want to use for this, but I’m not familiar with the notification system of nextcloud and truenas
it is a big deal. it fucks up even the remaining time estimation, but while the OS sees that write speed dropped to 0, the stick has literally frozen, it cannot even be read, or the directories browsed. I attribute this to crappy controllers inside the sticks, but of course I can’t actually know what’s at fault.
I don’t think it’s about the speed of my PC. My PC was at most mid range when I built it ~4 years ago. and if I plug in a 10+ years old 2 GB flash drive (and other sizes, there’s still a few around), it won’t do that, instead it’ll have a slow but steady write speed, still being readable while I copy to it.
why would you block reddit results? it’s often useful (at least when related to tech, possibly other topics too). I would recommend to install libredirect instead, which redirects reddit to a libreddit/redlib frontend
it only works for hiding ads, it is powerless to protect any of your privacy anymore. ublock origin is much more than an adblocker, but ubo lite is basically just google’s mockery
would running nut-monitor in the VMs fit your use case?
windows 11 is not only about irreversible breaking changes
did any of them do the write fast for 5 seconds, then freeze for 10 seconds shit? that’s the worst when a pendrive does that, and I’ve experienced that with multiple drives
apple and google is just a small part of the problem. using a debit card is not much better either
oh, that’s good to know! iirc that’s the same reason it happens on windows too
oh, that’s good to know! iirc that’s the same reason it happens on windows too
oh yeah now that you say, SMB/CIFS mounted share if connection is no more. when I experienced this, it was temporary though, because there’s a timeout which is half (or double?) of the configurable reconnection timeout. but now that I think of it, I’m not sure if it made it unkillable.
killall just kills all instances of a program, not everything.
and also, long pressing the power button should just shut it down, no?
on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.
I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.
only if that feature wouldn’t have a massive memory leak… can’t update even to 10.9 because it crashes the whole system the first time it tries to rescan a library.
there’s an issue, and they have a hard time figuring out the problem.
yes, that
that does not mean javascript is essential, and mox’s point is still very valid.
using WASM instead of JS is not better either. you simply don’t need any clientside executable code on a read-only view of a page
you should be able to turn it up always, to some extent. it’s in the settings on web
for example by being aware that the format is harmful to psychological health
oh, you’re right. still, my advice should be able to solve that