Tip: opening and closing ports needed by a systemd service

Sun, 18 Oct 2015 16:54:25 +0000

Recently I’ve been testing out murmur, http://wiki.mumble.info/wiki/Main_Page server component, on my CentOS 7 server. Murmur requires specific ports being open to operate, and when using it I would open them manually, and close them after the session had been completed.

I found it pretty tedious: I wanted to wrap it into a single call to the service, so I could enable my user (via sudoers) to be able to start and stop the service without worrying about elevating permissions to start and stop the firewall. After reading a bit systemd’s documentation I found about ExecStartPre and ExecStopPost that would work perfectly for the job.

Systemd and KDE Workspaces in openSUSE 12.3

Sat, 15 Dec 2012 14:01:31 +0000

openSUSE is migrating to the use of systemd for the upcoming 12.3 version, given the difficulties that emerged in trying to co-maintain two different init systems (SysV + systemd). While I am not going into the details of this choice (I leave this to more informed people), this has some consequences for software higher in the stack.

As ConsoleKit is deprecated, systemd offers its own daemon to keep track of sessions and assigned seats in a system. However, the KDE Workspaces rely on ConsoleKit to handle user switching, reboot, shutdown and a lot of ther things. Removing ConsoleKit would mean that users would suffer feature loss. On the other hand, with something that’s been deprecated and no longer actively worked on, you have issues with maintenance.

Systemd on dennogumi.org

Tip: opening and closing ports needed by a systemd service

Systemd and KDE Workspaces in openSUSE 12.3