[systemd-devel] systemd-userdbd and other stuff running all the time

[Reindl Harald]

is taht growing amount of services running on all systems really
necessary and why are things like "repart.service" and "homed.service"
are started "static" which makes the concept of enable/disable things
more and more obsolete

7.4 MB is a lot and i don't see any issue by just mask
"systemd-userdbd.service" and "systemd-userdbd.socket" on sever systems
at the moment, but who knows how deep the dependencies will become in
the future

lrwxrwxrwx 1 root root    9 2020-05-28 09:06 systemd-homed.service ->
/dev/null
lrwxrwxrwx 1 root root    9 2020-07-06 17:45 systemd-repart.service ->
/dev/null
lrwxrwxrwx 1 root root    9 2020-08-06 18:48 systemd-timesyncd.service
-> /dev/null
lrwxrwxrwx 1 root root    9 2020-08-24 12:47 systemd-userdbd.service ->
/dev/null
lrwxrwxrwx 1 root root    9 2020-08-24 12:47 systemd-userdbd.socket ->
/dev/null

[root at srv-rhsoft:~]$ systemctl status systemd-userdbd
● systemd-userdbd.service - User Database Manager
     Loaded: loaded (/usr/lib/systemd/system/systemd-userdbd.service;
static; vendor preset: disabled)
     Active: active (running) since Mon 2020-08-24 12:45:34 CEST; 48min ago
TriggeredBy: ● systemd-userdbd.socket
       Docs: man:systemd-userdbd.service(8)
   Main PID: 719025 (systemd-userdbd)
     Status: "Processing requests..."
      Tasks: 4 (limit: 512)
     Memory: 7.4M
        CPU: 253ms
     CGroup: /system.slice/systemd-userdbd.service
             ├─719025 /usr/lib/systemd/systemd-userdbd
             ├─725718 systemd-userwork
             ├─725842 systemd-userwork
             └─725843 systemd-userwork