Comments on: Install Cockpit on Debian 9 https://www.rosehosting.com/blog/install-cockpit-on-debian-9/ Premium Linux Tutorials Since 2001 Fri, 03 Jun 2022 08:33:39 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: admin https://www.rosehosting.com/blog/install-cockpit-on-debian-9/#comment-48501 Mon, 16 Nov 2020 08:11:31 +0000 https://www.rosehosting.com/blog/?p=31434#comment-48501 In reply to Sergio.

Try to use the following command:
systemctl enable --now cockpit.socket

]]> By: Sergio https://www.rosehosting.com/blog/install-cockpit-on-debian-9/#comment-48500 Mon, 16 Nov 2020 00:46:03 +0000 https://www.rosehosting.com/blog/?p=31434#comment-48500 There’s maybe a missing step in your tutorial, I’m running vanilla debian 9:

systemctl enable cockpit
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit’s
.wants/ or .requires/ directory.
2) A unit’s purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, …).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.

¿can you point me out in the right direction?

]]>