scx-upstream/services
Piotr Gorski 22e775842a
Make meson.build more readable
Signed-off-by: Piotr Gorski <lucjan.lucjanov@gmail.com>
2024-01-29 17:14:39 +01:00
..
journald@sched-ext.conf Increase log size to 25M 2024-01-19 21:30:33 +01:00
meson.build Make meson.build more readable 2024-01-29 17:14:39 +01:00
README.md Update README.md 2024-01-27 00:59:23 +01:00
scx systemd-services: add one service for all schedulers and config file 2024-01-27 00:41:00 +01:00
scx.service systemd-services: add one service for all schedulers and config file 2024-01-27 00:41:00 +01:00

A Quick Start Guide

This guide provides instructions for running the SCX schedulers as a systemd service and checking its logs.

Getting Started

At the very beginning, configure the /etc/default/scx file:

  • in the SCX_SCHEDULER variable, select the scheduler you are interested in

  • in the SCX_FLAGS variable, specify the flags you want to add. To do this, execute and read what flags you can add.

scx_SCHEDNAME --help

To start the SCX scheduler at boot, you need to run the systemd service as root. Here are the steps:

  • Enable the service:
systemctl enable scx.service
  • Start the service:
systemctl start scx.service

Alternatively, you can use a shortened version of these commands:

systemctl enable --now scx.service
  • To check the status of the service, use the following command:
systemctl status scx.service

Checking Journald Logs

The SCX schedulers do not log to the default journald namspace. Instead, they save logs in a dedicated sched-ext namespace. This is where you should look for information about possible errors.

  • To view the logs, use the following command:
journalctl --namespace=sched-ext
  • To find logs from another system startup and identify when a potential error might have occurred, use:
journalctl --namespace=sched-ext --list-boots
  • To verify the amount of space taken up by the logs, use:
journalctl --namespace=sched-ext --disk-usage