[[startup]]= Start upCockpit's `+cockpit-ws+` component is what the browser connects to andit typically starts on demand viahttps://www.freedesktop.org/wiki/Software/systemd/[`+systemd+`] socketactivation.The actual `+cockpit.service+` and `+cockpit-ws+` process will start ondemand when a browser accesses the `+cockpit.socket+`,xref:listen.adoc[usually on port 9090]. Once a user logs in then a`+cockpit-bridge+` process will be started in a Linux user loginsession.Only systems that you connect to with your browser need to have the`+cockpit.socket+` enabled. For systems that you add through hostswitcher the bridge is started via SSH on demand.[[startup-shutdown]]== Process exitThe `+cockpit-bridge+` process will exit when the user logs out. Inaddition, after 10 minutes of inactivity, the `+cockpit-ws+` processwill exit on its own. The browser will automatically disconnect if itfails to hear from the `+cockpit-ws+` process for 30 seconds.[[startup-boot]]== Boot start upTo make Cockpit available by default after system boot the`+cockpit.socket+` needs to be enabled:....$ sudo systemctl enable cockpit.socket....If you wish to not have Cockpit available by default via a browser, thenthe `+cockpit.socket+` should be disabled:....$ sudo systemctl disable cockpit.socket....