Go to file
nephros 3b4b3dfdf4 Version bump 2023-08-05 00:25:07 +02:00
doc add systemd dbus documentation 2022-07-11 08:36:44 +02:00
icon_src icon update 2022-06-27 15:50:43 +02:00
icons Correct build files 2023-08-05 00:22:42 +02:00
qml Fix Share menu option 2023-08-05 00:21:42 +02:00
rpm Version bump 2023-08-05 00:25:07 +02:00
sailjail expand permissions for system mode 2023-08-04 20:05:54 +02:00
translations Update Translations 2023-08-05 00:18:26 +02:00
.gitignore modified: .gitignore 2022-07-04 14:59:19 +02:00
LICENSE Initial commit 2022-06-25 13:02:19 +02:00
README.md update README 2022-11-19 22:16:26 +01:00
Screenshot_001.jpg add screenshots 2022-07-05 16:15:39 +02:00
Screenshot_002.jpg add screenshots 2022-07-05 16:15:39 +02:00
Screenshot_003.jpg add screenshots 2022-07-05 16:15:39 +02:00
Screenshot_004.jpg add screenshots 2022-07-05 16:15:39 +02:00
Screenshot_005.jpg add screenshots 2022-07-05 16:15:39 +02:00
build.sh clean icon dir before build 2022-07-13 17:05:59 +02:00
harbour-sailord.desktop Modernize .desktop file 2023-08-03 15:16:32 +02:00
harbour-sailord.pro Correct build files 2023-08-05 00:22:42 +02:00


SailorD - a SystemD Manager for Sailfish OS

SailorD shows and conreols interesting systemd units, and can act as a simple monitor for them.

Notifications are triggered if one of them goes into 'failed' state. The app must be running for monitoring or notifications to happen.


  • list Units of type: service, mount, timer, path
  • show status in listing and additional properties on click
  • start/stop/enable/disable units (experimental)
  • switch between Session and System DBUS (experimental)
  • show alerts/notifications when an unit goes into "failed" state
  • view the unit file and send it to another app

Some words of warning:

If you enable "Unit Control", i.e. the feature to start/stop/... unit, you should have a thorough understanding of what the different states and service types mean and how to interpret them.

On first view, you might see many services in some kind of "not running" state. For most of them this is okay and normal. Do not try to manually start them. (Things like oneshot or dbus-activated services are not running until triggered.)
Sometimes even a failed state is okay and normal - e.g. apparently dismissed alarms are implemented as a service that fails (and restarts) until the alarm is aquitted.

Conversely, stopping or disabling running services may also have unintended consequences, for obvious and not-so-obvious reasons. This may range from application not launching (e.g. because you stopped a booster service) to your phone not booting any more.

The author(s) of this app can not and will not support such issues caused by usage of SailorD.

Caveat emptor.

Internally, systemd's D-Bus interfaces are used, so any information listed, and actions taken are subject to that interface's permission setup.

See the systemd Documentation for details if interested.

License: Apache-2.0