Tianon Gravi

It's also a round-robin group of servers, so bad luck should usually be transitory unless you've got a firewall or something like that blocking in between.

The spec requirements of this should be about the same as the original -- 1GB of RAM or more, and any Debian-compatible system should be supported (which is the majority...

We don't have any unambiguously defined targets for the runtime footprint (just "small") -- as-is, it's a very, very minimal Debian installation (base on the "minbase" debootstrap variant), so it...

Probably because for almost all users of this package, the only time `cgroupfs-umount` is ever used is at shutdown (and likely the only time it will ever actually succeed in...

(Additionally, these days one is hard-pressed to find users who don't already have cgroups mounted by systemd and friends, so this package/these scripts aren't getting much use _or_ attention. :+1:)

While this is interesting, and I can see how it's useful for the particular use case of running systemd inside a container on a non-systemd host, I'm not sure that...

As I mentioned via email, the script isn't much more than checking `/proc/cgroups` and running a few `mount` commands based on the result, so if it's segfaulting on your system,...

You'll have to recompile your kernel -- if it's not compiled in, that's not something that can be added at runtime, as far as I know.

Ah, indeed. I would be quite happy with that functionality of the feature. I was unsure about that being the correct procedure because it seemed like when I tried it,...

Hmm, oh well. I must have screwed something up. Thanks for explaining, though!