Integrated client/server solution
From a Distance
As a rule, you will not want to manage the Karoshi server directly on the system's desktop, but administer the services from a workstation on the intranet. It does not have to use Linux. To do this, call up the address https://<Server-IP>:50001 in the remote computer's web browser.
Since access to the Karoshi server is exclusively encrypted via HTTPS, a security warning appears the first time you try to access it in the web browser; you need to set up an exception for this. Then authenticate against the server in the usual way with your username and password.
Division of Labor
Since Karoshi lets you distribute the server services across several computers on the intranet, you may need to assign maintenance tasks to several administrators, especially for larger infrastructures. Even in schools, several teachers might manage the different server systems. For this purpose, the primary admin creates additional administrator accounts that fill three roles under Karoshi. In addition to primary administrators, there are conventional admins and technicians.
Primary administrators have access to the entire feature set and can also make other users administrators. While traditional admins have access to the entire system, they are not allowed to grant or revoke administrator privileges to other users. In the role of technician, users only have access to selected administration areas.
Clients
The client for your workstations can also be found on the project site. Since the developers have coordinated the client and server, the client does not require any complicated network configuration work. After booting the client from the DVD, select in the GRUB boot menu whether you want the system to boot in live mode or to complete the installation directly.
The live system opens a simple Xfce desktop with some icons on the desktop; the Karoshi Setup starter lets you configure the system. If you decide to install the software, a lean Ubiquity installer is fired up and quickly bundles the operating system onto your hard disk.
After a restart, the configuration routine, which opens a connection to the router, is automatically loaded. In addition, the system tries to directly connect to the domain controller; it should also be logged onto the intranet at this point. The intranet connection must be via Ethernet, however. WiFi access did not work in our lab. Although the routine detects the WiFi interface and also sets up the corresponding kernel module, it does not offer a dialog for entering the SSID or the WPA2 key.
The client setup routine prompts you for the username and password of a user already created on the server, as well as some server data during the initial configuration. You must have created at least one other user on the Karoshi server in addition to the administration account. After entering the corresponding access credentials, the client routine configures access to the server, restarts the system, and logs on to the server. The client desktop shows more icons, because now the Samba shares also appear.
When creating the client user on the server, you will want to carefully assign the appropriate groups to avoid clients gaining access to folders that later on will not be intended for them. You can set these options in the Members column of the User and Groups | Group Management dialog, where you set the desired configuration for each group member.
The administrator can also see which users are logged on to a server using the Client | Client connections option in the configuration dialog. After selecting a server, the system lists the currently active computers. On the Linux client itself, you can open the server's web configuration with the Karoshi Management starter on the desktop.
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
NVIDIA Released Driver for Upcoming NVIDIA 560 GPU for Linux
Not only has NVIDIA released the driver for its upcoming CPU series, it's the first release that defaults to using open-source GPU kernel modules.
-
OpenMandriva Lx 24.07 Released
If you’re into rolling release Linux distributions, OpenMandriva ROME has a new snapshot with a new kernel.
-
Kernel 6.10 Available for General Usage
Linus Torvalds has released the 6.10 kernel and it includes significant performance increases for Intel Core hybrid systems and more.
-
TUXEDO Computers Releases InfinityBook Pro 14 Gen9 Laptop
Sporting either AMD or Intel CPUs, the TUXEDO InfinityBook Pro 14 is an extremely compact, lightweight, sturdy powerhouse.
-
Google Extends Support for Linux Kernels Used for Android
Because the LTS Linux kernel releases are so important to Android, Google has decided to extend the support period beyond that offered by the kernel development team.
-
Linux Mint 22 Stable Delayed
If you're anxious about getting your hands on the stable release of Linux Mint 22, it looks as if you're going to have to wait a bit longer.
-
Nitrux 3.5.1 Available for Install
The latest version of the immutable, systemd-free distribution includes an updated kernel and NVIDIA driver.
-
Debian 12.6 Released with Plenty of Bug Fixes and Updates
The sixth update to Debian "Bookworm" is all about security mitigations and making adjustments for some "serious problems."
-
Canonical Offers 12-Year LTS for Open Source Docker Images
Canonical is expanding its LTS offering to reach beyond the DEB packages with a new distro-less Docker image.
-
Plasma Desktop 6.1 Released with Several Enhancements
If you're a fan of Plasma Desktop, you should be excited about this new point release.