@j_r It has imo some overspecific service hardening and tmpfiles setup that breaks non-default use cases in hard to debug ways.
e.g. I thought, hey, I'll just set the consumption dir env variable manually so I don't have to disable its tmpfiles settings for it. This made the services restart and fail endlessly with no delay, driving cpu to 100% and making debugging on my not that powerful hardware even more painful.
@fugi oh okay, I probably have a very standard use case then. But yeah very specific service hardening is a thing that I also experienced a few times with other NixOS modules
