Description of problem:
Let's get the ball rolling on this one...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 546442 [details]
Native systemd service file for flow capture
Note that users should copy the unit file to /etc/systemd/system directory and add/edit any options there which is why I did not include /etc/sysconfig/flow-capture as an environment file.
Okay. Who else is using flow-capture?
I was thinking about how to do this better. One option would be to include a template for flow-capture@.service, and then it will be like that-
/etc/sysconfig/flow-capture.NAME has options
and then you enable flow-capture@NAME.service
/etc/sysconfig is Red Hat specific while copying flow-capture to /etc/systemd/system/flow-capture-$NAME.service is distro agnostic for all distro using systemd thus more correct way of handling this and more likely to be accepted by upstream when you submit it there.
Ofcourse you can ship both the flow-capture.service and a template flow-capture@.service with specifiers and have users link to that template...
Paul any objection to my making this change? I can change the unit file to source the sysconfig.
No objections. Sorry it took so long to reply. Please, if you can, make the sysconfig change.
No worries, done, with sysconfig. Thanks!