> systemctl enable cockpit.socket
> systemctl start cockpit.socket
There is slight difference on when the service gets activated (on
startup vs. on first access), but I guess either way is fine.
The documentation indeed mentions the socket way:
http://cockpit-project.org/guide/133/startup.html
On Tue, Mar 13, 2018 at 4:14 PM, Martin Sivak wrote:
> Hi,
>
> make sure the service is actually started and the firewall is
> configured properly:
>
> systemctl status cockpit
> firewall-cmd --list-all
>
> You can make sure all is fine by doing the following:
>
> systemctl enable cockpit
> syste
Hi Martin,
thanks. It works. I just wantd to known if any special 'ovirt' commands
are needed, seems not.
regards
Peter
On 13/03/2018 16:14, Martin Sivak wrote:
> Hi,
>
> make sure the service is actually started and the firewall is
> configured properly:
>
> systemctl
Hi,
make sure the service is actually started and the firewall is
configured properly:
systemctl status cockpit
firewall-cmd --list-all
You can make sure all is fine by doing the following:
systemctl enable cockpit
systemctl start cockpit
firewall-cmd --add-service=cockpit --permanent
firewall-
4 matches
Mail list logo