Bug 767392

Summary: Provide native systemd service
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: flow-toolsAssignee: Paul P Komkoff Jr <i>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gwync, i
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-24 18:29:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 751869    
Description Flags
Native systemd service file for flow capture none

Description Jóhann B. Guðmundsson 2011-12-13 23:07:20 UTC
Description of problem:

Let's get the ball rolling on this one...


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Jóhann B. Guðmundsson 2011-12-13 23:09:15 UTC
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.

Comment 2 Paul P Komkoff Jr 2011-12-14 13:46:37 UTC
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

Comment 3 Jóhann B. Guðmundsson 2011-12-14 14:10:13 UTC
/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...

Comment 4 Gwyn Ciesla 2012-04-19 19:51:17 UTC
Paul any objection to my making this change?  I can change the unit file to source the sysconfig.

Comment 5 Gwyn Ciesla 2012-04-24 14:07:13 UTC

Comment 6 Paul P Komkoff Jr 2012-04-24 16:06:39 UTC
No objections. Sorry it took so long to reply. Please, if you can, make the sysconfig change.

Comment 7 Gwyn Ciesla 2012-04-24 18:29:18 UTC
No worries, done, with sysconfig.  Thanks!