websites/dennogumi.org-archive
Archived
1
0
Fork 0
Code Releases Activity

Clarify that the OS used is CentOS 7

Browse source
This commit is contained in:
Luca Beltrame 2015-10-18 17:06:31 +02:00
parent 779cf42d25
commit 026aa50896
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown
View file

@ -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.