From 026aa508969ec4e1ebe3fb98bc203d836f10c713 Mon Sep 17 00:00:00 2001 From: Luca Beltrame Date: Sun, 18 Oct 2015 17:06:31 +0200 Subject: [PATCH] Clarify that the OS used is CentOS 7 --- ...ening-and-closing-ports-needed-by-a-systemd-service.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown b/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown index 23a4011..c997778 100644 --- a/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown +++ b/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown @@ -10,7 +10,7 @@ tags: title: 'Tip: opening and closing ports needed by a systemd service' --- -Recently I've been testing out murmur, [http://wiki.mumble.info/wiki/Main_Page](Mumble's) server component. 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. +Recently I've been testing out murmur, [http://wiki.mumble.info/wiki/Main_Page](Mumble's) 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](http://www.freedesktop.org/software/systemd/man/systemd.service.html) I found about ``ExecStartPre`` and ``ExecStopPost`` that would work perfectly for the job.