https://github.com/Whonix/swap-file-creator/commit/cba4e22135737f2966766711bfb606c0f905a4c4

I won't do create a systemd unit as replacement for ./packages/ksm/etc/init.d/ksm myself, because the package does not get installed by default and because there is now https://packages.debian.org/sid/ksmtuned. Patches welcome. @HulaHoop

control-port-filter-python - added systemd service:
https://github.com/Whonix/control-port-filter-python/commit/d8e1d5711d2a71a9ab638c03e84a0d9b48d7ae48
Could you review that systemd unit please, @nrgaway?

May be helpful for systems configuration. Debian directory structure could be different:

https://access.redhat.com/articles/754933

Paths of the ksm/ksmtuned services on RHEL family:
/usr/lib/systemd/system/ksmtuned.service 
/usr/lib/systemd/system/ksm.service 

Is adding this for ksmtuned a matter of emulating your commit?

No.

In T106#3482, @HulaHoop wrote:

May be helpful for systems configuration. Debian directory structure could be different:

https://access.redhat.com/articles/754933

Paths of the ksm/ksmtuned services on RHEL family:
/usr/lib/systemd/system/ksmtuned.service 
/usr/lib/systemd/system/ksm.service 

Is adding this for ksmtuned a matter of emulating your commit?

Debian systemd layout is same as fedora.

If you plan on overriding an upstream packages unit files, there are a few options:

1. If you just adding a path or something, add a snippet
2. place overridden unit file in /etc/system/systemd (This is wehre local modifications go). If you are using another name than the original systemd file, add an Alias in the install section

[Install]
WantedBy=multi-user.target
Alias=qubes-network.service

Then you would need to disable and enable the service to take effect.

add a snippet

Can you please elaborate?

@nrgaway?

I am not sure if we should remove old sysvinit scripts from packages once systemd units are available. They don't conflict. And someone might wish to use/port the package on systems without systemd. Mailed Paul Wise from Debian what the best practice about this is.

In T106#3814, @Patrick wrote:

add a snippet

Can you please elaborate?

From https://lwn.net/Articles/542609/

Configuration of unit files may now be extended via drop-in
files without having to edit/override the unit files
themselves. More specifically, if the administrator wants to
change one value for a service file foobar.service he can
now do so by dropping in a configuration snippet into
/etc/systemd/systemd/foobar.service.d/*.conf. The unit logic
will load all these snippets and apply them on top of the
main unit configuration file, possibly extending or
overriding its settings. Using these drop-in snippets is
generally nicer than the two earlier options for changing
unit files locally: copying the files from
/usr/lib/systemd/system/ to /etc/systemd/system/ and editing
them there; or creating a new file in /etc/systemd/system/
that incorporates the original one via ".include". Drop-in
snippets into these .d/ directories can be placed in any
directory systemd looks for units in, and the usual
overriding semantics between /usr/lib, /etc and /run apply
for them too.

Great stuff. Needless to say I am a huge fan of drop-in snippets.

In T106#3920, @Patrick wrote:

I am not sure if we should remove old sysvinit scripts from packages once systemd units are available. They don't conflict. And someone might wish to use/port the package on systems without systemd. Mailed Paul Wise from Debian what the best practice about this is.

They can confilct and it is a PITA to debug. You can keep the sysv init scripts in your Debian package but don't install them. I just went though that with network-manager; was wondering why 2 of them were popping up.

Also in order for a systemd unit file to override the sysv init one, you have to first disable it, then re-enable it and they should be both of the same name or you may need to set an alias

whonixcheck:
https://github.com/Whonix/whonixcheck/commit/c91dc77a1dae49be4635380e330fdfda9cb4ada2

msgcollector:
https://github.com/Whonix/msgcollector/commit/ff50e3c286fea6663f6d45906411177080f9a1bd

bootclockrandomization:
https://github.com/Whonix/bootclockrandomization/commit/77d3e620017dd067e1660e7bebf582f042484c47

timesanitycheck:
https://github.com/Whonix/timesanitycheck/commit/03640195a9c6b18ae1259b62a44994c32619add9

swap-file-creator:
https://github.com/Whonix/swap-file-creator/commit/a8f58cf240763599613e3ab4598a3e7e34400caa

vbox-disable-timesync, no port to systemd, because upstream does not provide a systemd unit, diverting it, more robust implementation that is compatible with systemd:
https://github.com/Whonix/vbox-disable-timesync/commit/958086eb0d55e0669492ab16ec15d810a533f597

sdwdate:
https://github.com/Whonix/sdwdate/commit/62c32cb2cd2bb9f518bb8b5cd7c84906a4294f1e

timesync:
https://github.com/Whonix/timesync/commit/270a1f3fb397deda261e11e5d4c38e435bbb40d4

sdwdate pidfile is still missing and timesync complains about that. Working on that.

Fixed that:

• https://github.com/Whonix/sdwdate/commit/f1f8d4c41a55241b46aa4a847aab168c09a132c0
• https://github.com/Whonix/sdwdate/commit/9b722218b9a7911cf214c0f3c5b482f0e57d2ba3

TODO: most should use SuccessExitStatus.

In T106#4449, @Patrick wrote:

TODO: most should use SuccessExitStatus.

Done:

• https://github.com/Whonix/sdwdate/commit/2f7960a0217605eaf05950ca467df4f2484a3f57
• https://github.com/Whonix/whonixcheck/commit/7091c9d136f2a7a0051f6f6f94e4a5a86ef1763f

fix, renamed lib/systemd/system/timesanitycheck to lib/systemd/system/timesanitycheck.service:
https://github.com/Whonix/timesanitycheck/commit/fee20a038d26f281fbbcfe904ece3bd11f556bf9

fix, lib/systemd/msgcollector.service -> lib/systemd/system/msgcollector.service - https://phabricator.whonix.org/T106:
https://github.com/Whonix/msgcollector/commit/a708e9180eb22038aad68e5fb0990a4122eb9daa

fix:
https://github.com/Whonix/msgcollector/commit/8132e8a8ffaeede8557f9482ff64464c5c998296

systemd unit: added 'KillMode = process', because the daemon handles terminating child processes itself - https://phabricator.whonix.org/T106:
https://github.com/Whonix/sdwdate/commit/3a14c5ecc0649c66df43a396a20a47da4b27383d

systemd unit: added 'KillMode = process', because the daemon handles terminating child processes itself - https://phabricator.whonix.org/T106
https://github.com/Whonix/whonixcheck/commit/7cb379710c081a3e14a68b41d1f30c68ca5f1b0e

systemd unit: added 'Before=rads.service' to prevent output by rads mixing up with output by whonix-initializer and to prevent the login manager from starting before whonix-initializer rebooted the system:
https://github.com/Whonix/whonix-initializer/commit/80dbb25732d58cab3a3abbe7634345d42848d4a5

when timesync (sdwdate gui plugin) is installed, then the sdwdate.service needs an additional 'Requires = msgcollector.service' - https://phabricator.whonix.org/T106:
https://github.com/Whonix/timesync/commit/e1e88c84c07697825a4aea14ac1c723192a58075

systemd unit: added 'Before=control-port-filter-python.service:
https://github.com/Whonix/whonix-initializer/commit/ace6738ef5ebb00ac5bc645d80577011b873e506

more work on systemd support - https://phabricator.whonix.org/T106:
https://github.com/Whonix/timesync/commit/0a76d86a8e37ae9691374da69bdef452b6def7cc

systemd unit: added 'StandardOutput=tty' for better look and feel. - https://phabricator.whonix.org/T106
https://github.com/Whonix/swap-file-creator/commit/f49f572e5a06ed33eeacc5647f0f85751cc611b9

more work on systemd support - https://phabricator.whonix.org/T106:

• https://github.com/Whonix/sdwdate/commit/0f6e50748eaeab34f9f00ce7dfbd80e980cb2a5b
• https://github.com/Whonix/timesync/commit/b506ea4186a50bb50ae9b198deefaf2c9a7ca5d8

systemd unit: added 'Before=tor.service' and 'After=swap-file-creator.service' for better look and feel. - https://phabricator.whonix.org/T106:
https://github.com/Whonix/whonix-initializer/commit/0c1490942edd4c58207980785bb658afa163cb15

systemd unit: added 'Before=graphical.target' and 'Before=getty.target' - https://phabricator.whonix.org/T106:
https://github.com/Whonix/msgcollector/commit/ab24bd261d8ac2027f6a3ad85da4b4a3d416b044