On 2020-01-13 10:52, john doe wrote:
What about 'systemctl disable gdm'?
Doesn't work, either.
"systemctl status gdm" claims that gdm is masked (or disabled),
but nevertheless it *is* started.
root@usbpc:~# systemctl status gdm
* gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; masked; vendor preset:
enabled)
Active: active (running) since Mon 2020-01-13 11:23:37 CET; 49s ago
Process: 10440 ExecStartPre=/usr/share/gdm/generate-config (code=exited,
status=0/SUCCESS)
Main PID: 10446 (gdm3)
Tasks: 3 (limit: 4915)
Memory: 7.0M
CGroup: /system.slice/gdm.service
`-10446 /usr/sbin/gdm3
Jan 13 11:23:37 usbpc systemd[1]: Starting GNOME Display Manager...
Jan 13 11:23:37 usbpc systemd[1]: Started GNOME Display Manager.
Jan 13 11:23:37 usbpc gdm-launch-environment][10454]:
pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by
(uid=0)
The man page for "systemctl mask" says
"Mask one or more units, as specified on the command line. This will
link these unit files to /dev/null, making it impossible to start
them. This is a stronger version of disable, since it prohibits all
kinds of activation of the unit, including enablement and manual
activation."
"impossible" and "prohibits all kinds of activation of the unit" seems
to be unambigous to me.
Harri
