mirror of
https://github.com/sched-ext/scx.git
synced 2024-11-25 04:00:24 +00:00
|
|
||
|---|---|---|
| .. | ||
| journald@sched-ext.conf | ||
| meson.build | ||
| README.md | ||
| scx_central.service | ||
| scx_flatcg.service | ||
| scx_nest.service | ||
| scx_pair.service | ||
| scx_qmap.service | ||
| scx_rustland.service | ||
| scx_rusty.service | ||
| scx_simple.service | ||
| scx_userland.service | ||
A Quick Start Guide
This guide provides instructions for running the SCX schedulers as a systemd service and checking its logs.
Getting Started
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_SCHEDNAME
- Start the service:
systemctl start scx_SCHEDNAME
Alternatively, you can use a shortened version of these commands:
systemctl enable --now scx_SCHEDNAME
- To check the status of the service, use the following command:
systemctl status scx_SCHEDNAME
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