Red Hat Bugzilla – Bug 697653
Providing native systemd file for upcoming F15 Feature Systemd
Last modified: 2016-01-31 20:54:58 EST
Created attachment 493004 [details]
Native systemd service file for psacct
Description of problem:
The attached file is a native systemd file for upcoming F15 Feature 
Please read  on how to packaging and installing systemd Service files.
To learn more about Systemd daemon see .
To view old SysV with the new Systemd site by site see for your component see 
If you have any question dont hesitate to ask them on this bug report.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Moving systemd service RFEs to rawhide.
At this point, it is not appropriate in the Fedora 15 cycle to add these. Furthermore, at this point, we are still finalizing the packaging guidelines to handle SysV -> systemd upgrades.
We therefore request:
- wait until there are packaging guidelines (this will be announced on the devel list). This ensures that upgrades will work smoothly and we/you won't have to do multiple sets of changes.
- work on these sorts of changes for Fedora 16 where necessary, not Fedora 15, as we're trying to fix things for release.
- do *not* change a service from SysV to systemd in an existing release (such as Fedora 15), as this is the sort of behavior change that goes against our update policy, documented as https://fedoraproject.org/wiki/Updates_Policy
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
What's the current status on this?
We need this in rawhide the sooner the better.
Created attachment 510087 [details]
Spec file which introduce systemd unit file and drop SysV support for psacct.service
psacct-6.5.5-3.fc16 has been built ...
Please, test ...
Had to do a manual 'systemctl enable psacct' to actually get it started. So somebody needs to work on the packaging guidelines a bit more, I suspect - maybe it needs to do a 'chkconfig' for the SysV and do an 'enable' if the old SysV init file was enabled? Of course, this gets hairy - in the preinst RPM script, you don't have the 'psacct.service' file in place yet so you cant do a "systemctl enable", and in postinst the SysV script is gone... I'll leave that perplexing detail to somebody who understands RPM better than I.
has psacct been granted exception from fesco to be enabled by default?
And note on updates from legacy to sysv init script end users will need to enable the service had it been previously enabled themselfs again..
T(In reply to comment #7)
> has psacct been granted exception from fesco to be enabled by default?
> And note on updates from legacy to sysv init script end users will need to
> enable the service had it been previously enabled themselfs again..
That is if it's not enabled by default..
Oh btw now that you ship native systemd service file for psacct you should close this bug as fixed to get it off the the bug tracker list radar ...
Oh, is *that* the criterion? "enabled by default", not "enabled on the system in question"? That would explain a lot of the pain I've had with services disappearing on me as they convert to systemd....
(If the release notes end up mentioning "you'll need to do a 'systemctl enable' for non-default stuff you turned on using chkconfig", that would address the issue I saw and you can close this bug)