You are not logged in.
Just wanted to know if i can disable this service since i don't use systemd-homed (which requires this service).
systemd-userdbd.service
│ ├─ 199 /usr/lib/systemd/systemd-userdbd
│ ├─1171 "systemd-userwork: waiting..."
│ ├─1180 "systemd-userwork: waiting..."
│ └─1181 "systemd-userwork: waiting..."
Even after disabling it my setup runs completely fine so i was wondering is it necessary?
Last edited by idkprbly (2024-04-23 12:28:36)
Offline
Arch has online manpages: https://man.archlinux.org/man/core/syst … erdbd.8.en
Offline
Well i read those manpages but i still cant figure out the importance of this service. Its enabled by default after fresh arch install so i guess its quite important.
Offline
Arch provides upstream man pages. And systemd man pages are full of doublespeak and meaningless technobabble and do not answer the OP's question at all.
I can't really answer it except to say that you certainly can get rid of this as long as you get rid of all of systemd. However, if you want / need to keep systemd, it's an open question, as systemd is not at all modular: surprising breakage can arise from disabling things that really have no reason to run on your system.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
The manpage links https://systemd.io/USER_RECORD/
systemd-userdbd.service is a small service that can translate UNIX/glibc NSS records to these JSON user records. It also provides a unified Varlink API for querying and enumerating records of this type, optionally acquiring them from various other services.
systemd optionally processes user records that go beyond the classic UNIX (or glibc NSS) struct passwd.
Idk whether you *need* that but it's effectively more LennartOS and it's neither enabled nor running here and it is socket activated, so not "enabled by default" anywhere.
The socket isn't enabled either, it comes w/ an "enabled" preset, but that's ignored by archlinux.
I do however not know whether that's actually true for recent ISOs, but let's see
systemctl status systemd-userdbd.service systemd-userdbd.socket
For the records: this is the archlinux install iso from http://archlinux.org/download/ and you didn't run some 3rd party installer script either?
Offline
It may be "loaded" and "preset: enabled" even if "disabled". Which is, of course, crystal clear.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Nobody's arguing that systemd isn't a convoluted mess that suffers from mission creep because lennart is ultimately trying to turn it into windows.
Offline
Sorry for late reply, i reinstalled arch(i don't use any script) and executed the following command:
systemctl status systemd-userdbd systemd-userdbd.socket
and this is the output i got:
● systemd-userdbd.service - User Database Manager
Loaded: loaded (/usr/lib/systemd/system/systemd-userdbd.service; indirect; preset: dis
abled)
Active: active (running) since Sun 2024-03-03 22:34:59 IST; 1 month 16 d
ays ago
TriggeredBy: ● systemd-userdbd.socket
Docs: man:systemd-userdbd.service(8)
Main PID: 199 (systemd-userdbd)
Status: "Processing requests..."
Tasks: 4 (limit: 4371)
Memory: 4.6M (peak: 5.2M)
CPU: 166ms
CGroup: /system.slice/systemd-userdbd.service
├─199 /usr/lib/systemd/systemd-userdbd
├─814 "systemd-userwork: waiting..."
├─815 "systemd-userwork: waiting..."
└─816 "systemd-userwork: waiting..."
Warning: some journal files were not opened due to insufficient permissions.
● systemd-userdbd.socket - User Database Manager Socket
Loaded: loaded (/
usr/lib/systemd/system/systemd-userdbd.socket; enabled; preset: e
nabled)
Active: active (running) since Sun 2024-03-03 22:34:58 IST; 1 month 16 d
ays ago
Triggers: ● systemd-userdbd.service
Docs: man:systemd-userdbd.service(8)
Listen: /run/systemd/userdb/io.systemd.Multiplexer (Stream)
CGroup: /system.slice/systemd-userdbd.socket
Warning: some journal files were not opened due to insufficient permissions.
My time settings are off but it show userdbd service to be enabled
Last edited by idkprbly (2024-04-20 08:22:31)
Offline
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
So the socket got enabled, https://gitlab.archlinux.org/archlinux/ … f5a16faa44
As stated in commit message, it is generally useful, and I see no reason not to ship it by default. People who don't want it can disable it on their own.
It's lightweight and generally useful, so it should be enabled by default.
https://github.com/systemd/systemd/issues/15175
systemd-userdbd cannot be disabled
systemd-userdbd cannot be disabled. When masking the service everything runs well again but this error appears in the logs due to the socket being blocked:
systemd-userdbd.socket: Socket service systemd-userdbd.service not loaded, refusing.
Failed to listen on User Database Manager Socket.Why is this service running in the first place?
I have no use for it and therefore it should be disabled by default until the user activates it.
So, counterpoint: no it's not.
Offline
Thanks, so i guess i will disable it post install as i dont have any use for that service.
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline