Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
Am 02.11.2019 um 08:47 schrieb John M. Harris Jr johnmh@splentity.com:
... I have no idea why I don't get an option to turn off that useless web UI.
Maybe because a lot of users regard Cockpit as useful or handy ?
BTW, do you know about these: https://www.sightwordsgame.com/speaking/common-courtesy/. ?
On 11/2/19 3:47 PM, John M. Harris Jr wrote:
Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
Not nice to denigrate the work of people who've worked to provide a service. Also, you may not like it but to label what others may find useful is also not called for.
Now, would you find it sufficient to simply do
systemctl disable cockpit.socket
Or is something else a bother to you?
On Saturday, November 2, 2019 2:19:22 AM MST Ed Greshko wrote:
On 11/2/19 3:47 PM, John M. Harris Jr wrote:
Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
Not nice to denigrate the work of people who've worked to provide a service. Also, you may not like it but to label what others may find useful is also not called for.
Now, would you find it sufficient to simply do
systemctl disable cockpit.socket
Or is something else a bother to you?
-- The key to getting good answers is to ask good questions.
A process wasting CPU cycles and RAM is not something that I find to be useful in the least, especially not on a system running from two flash drives in RAID1 on one of Dell's 11th generation servers. I'm sure some people, perhaps those who don't know how to manage a system themselves, would find this useful. For them, perhaps it'd be nice to have an option to pull in that bloat. It is not useful to me, and I'm sure others feel the same way.
That people worked on it does not make it useful. I'm sorry if people disagree with this, but it is the reality of the situation.
Regardless, disabling it did help, but I'd like to remove all of the bloat if possible. Is it tied in to a common package in the Server spin, like some things in GNOME are, or will removing the `cockpit` package not attempt to take half of the system with it?
On Saturday, November 2, 2019 1:43:37 AM MST Peter Boy wrote:
Am 02.11.2019 um 08:47 schrieb John M. Harris Jr johnmh@splentity.com:
... I have no idea why I don't get an option to turn off that useless web UI.
Maybe because a lot of users regard Cockpit as useful or handy ?
BTW, do you know about these: https://www.sightwordsgame.com/speaking/common-courtesy/. ?
It's possible that some people find it to be useful. I do not, and I don't think many people that are running this software on actual server hardware would either. I'm sorry if you don't like my wording, but I just want to remove something which is just useless bloat on my system. It is not only not useful to me, but is actively degrading the performance of my installation.
On 11/2/19 12:47 AM, John M. Harris Jr wrote:
Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
Did yours come enabled by default? I get the following message when I log in: Activate the web console with: systemctl enable --now cockpit.socket
However, if you want to remove it, just run: dnf remove --noautoremove cockpit*
On Saturday, November 2, 2019 12:16:46 PM MST Samuel Sieb wrote:
On 11/2/19 12:47 AM, John M. Harris Jr wrote:
Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
Did yours come enabled by default? I get the following message when I log in: Activate the web console with: systemctl enable --now cockpit.socket
However, if you want to remove it, just run: dnf remove --noautoremove cockpit*
Yep, came enabled by default. Thanks! I'll have to remember that option.
On 11/3/19 10:50 AM, Gordon Messmer wrote:
On 11/2/19 11:52 AM, John M. Harris Jr wrote:
It is not only not useful to me, but is actively degrading the performance of my installation.
Out of curiosity, how did you measure the performance impact of cockpit?
That's a good question.
cockpit.service is a static service. Nothing runs unless one connects to the cockpit.socket listening on port 9090.
I have 2 servers in VM's. One with, one without the cockpit.socket enabled.
On idle systems with no other services configured/running "top" shows load averages of
load average: 0.00, 0.00, 0.01
on both.
On Saturday, November 2, 2019 7:50:59 PM MST Gordon Messmer wrote:
On 11/2/19 11:52 AM, John M. Harris Jr wrote:
It is not only not useful to me, but is actively degrading the performance of my installation.
Out of curiosity, how did you measure the performance impact of cockpit?
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
The issue was not as much the CPU time as the I/O impact. This system was running on a RAID1 config of two USB 2.0 thumbdrives on the internal USB slots of an 11th gen Dell server. The performance impact was determined using `iostat` both before and after disabling the service. By the way, both cockpit.service and cockpit.socket were enabled by default.
On 11/3/19 1:04 PM, John M. Harris Jr wrote:
By the way, both cockpit.service and cockpit.socket were enabled by default.
That's odd.... While I've manually disabled the socket
[root@f31sd ~]# systemctl status cockpit.service ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:cockpit-ws(8)
Vendor preset for the service is "disabled"
[root@f31sd ~]# systemctl status cockpit.socket ● cockpit.socket - Cockpit Web Service Socket Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:cockpit-ws(8) Listen: [::]:9090 (Stream)
Vendor preset for the socket is "enabled" and I've disabled it on this system
[root@f31sd ~]# systemctl enable cockpit.service 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: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified.
Is what happens when one tries to enable cockpit.service since it is a static service.
Are you saying yours shows "enabled"?
Sat, 02 Nov 2019 00:47:15 -0700 "John M. Harris Jr" johnmh@splentity.com:
Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI.
You can mask it: systemctl mask cockpit
I threat the Cockpit as a software iDrac/iLO/iSomething. I prefer hardware for sure, but maybe it would provide useful someday.
-
Ed Greshko -
Gordon Messmer -
John M. Harris Jr -
Peter Boy -
Samuel Sieb -
Łukasz Posadowski