WhyJiffie

this can be useful, but hopefully it never becomes a default, it was enough of a pain when Windows was thinking that updates are more important than keeping the hibernated programs

even the outside?

for the inside I don't think it's a problem, it's hygienic

of course the eventual enforcement is left to the service provider (google) as it often is how it works. when you can't define something with 100% precision, you leave some room for interpretation. they can then decide what to do on a case by case basis.

totally clear. and exactly the subject is the broadest: harmful to anyone or anything

it seems they will, just not too soon

Oh you will. I know the name for a few months now and I still read it slurpnik

if they haven't defined it, then legally it is meant in the broadest sense, isn't it?

Drives only consume power on reads and writes, if your NAS spins them down as it should (and apparently QNAP *doesn't, which I didn't know).

not really. not all drives spin down by themselves, by default. and even if they do, it'll happen relatively long after reads and writes, a the while it'll consume power.

The problem seems to be that even with a perfectly clean slate, no services running, the system set up in their own RAID0 SSD pool, the HDD's, even with 0 bytes of data on them, are being pinged for access at least once a minute.

if it's for drive health stats, and the device runs linux, hd-idle could help. it only counts actual block device (so, storage) access as activity

edit: https://github.com/adelolmo/hd-idle

And don't think that SSD drives would do better - spinning disk drives generally have far better idle power than SSD does, and usually much better write power consumption.

I wonder if they can be "spinned down" like hard drives. their startup time would be much faster, so it's shutdown could even be on a tighter schedule. I mean probably they dont have an internal idle timer, but who cares if you can just have something like hd-idle that shuts it down according to a better schedule.

In my experience using a PC as a NAS, the power draw isn't necessarily the drives as they spin down when idle.

that's not always the default setup, especially with enterprise drives. also if you have some kind of monitoring, that can keep the drives from going down (for that, use linux hd-idle instead of drive internal idle timer), and it can also wake them up (for that, prometheus node exporter's smart collector first checks whether a drive is up, and only then collect stats). Interestingly, checking temps with smartctl always spins up my drives, while linux hwmon can give me live temp stats even while the drives are down

we should call them terrorists before they tag us as terrorists. Because that's what they are.