On Tue, Jul 02, 2024 at 10:01:54PM -0700, Darrick J. Wong wrote: > On Wed, Jul 03, 2024 at 06:31:24AM +0200, Christoph Hellwig wrote: > > On Tue, Jul 02, 2024 at 07:59:29PM -0700, Darrick J. Wong wrote: > > > CONFIG_XFS_ONLINE_SCRUB isn't turned on for the 6.9.7 kernel in sid, so > > > there shouldn't be any complaints until we ask the kernel team to enable > > > it. I don't think we should ask Debian to do that until after they lift > > > the debian 13 freeze next year/summer/whenever. > > > > I'm not entirely sure if we should ever do this by default. The right > > fit to me would be on of those questions asked during apt-get upgrade > > to enable/disable things. But don't ask me how those are implemented > > or even called. > > Some debconf magicks that I don't understand. :( A week's worth of digging later: Actually, no debconf magic -- Debian policy is to enable any service shipped in a package, by default: https://www.debian.org/doc/debian-policy/ch-opersys.html#starting-system-services "Debian packages that provide system services should arrange for those services to be automatically started and stopped by the init system or service manager." It's up to the sysadmin to disable this behavior, either by installing their own systemd preset file: https://manpages.debian.org/bookworm/systemd/systemd.preset.5.en.html that shuts off the services they don't want (or more likely enables only the ones they do want). Other people have proposed rc.d hacks: https://packages.debian.org/bookworm/policy-rcd-declarative-deny-all which prevent the postinst scripts from actually triggering the service. > A more declarative-happy way would be to make a subpackage that turns on > the background service, so the people that want it on by default can add > "Depends: xfsprogs-background-scrub" to their ... uh ... ansible? > puppet? orchestration system. Though I guess we /could/ decide to ship only the xfs_scrub_all.{service,timer} files in a totally separate package. But that will make packaging more difficult because now we have to have per-package .install files so that debconf knows where to put the files, and then we have to split the package scripts too. On Fedora it's apparently the other way 'round where one has to turn on services manually. --D
