Red Hat Bugzilla – Bug 695741
Providing native systemd file
Last modified: 2014-05-26 05:46:11 EDT
Created attachment 491506 [details]
Native systemd service file for dirsrv admin
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:
For upgrading - 389 packages do not automatically set the run levels - we require the user to do
chkconfig dirsrv on
we provide defaults but the user can override them
If we upgrade from sysVinit to systemd .services, will systemd preserve these run levels? Or is that simply not applicable to systemd .services?
Runlevels dont exist in systemd world and are things of the past and to fully crasp systemd its best to forget the old sysv stuff it's so much more powerful.
The[Install] section in a service file tells which target(s) the service will be activated on bootup if it has been enabled you can for example create an 389DS.target and boot that up with all the services a 389 Directory server should have.
you should run /usr/bin/systemd-sysv-convert --save $service during upgrades as is mentioned in https://fedoraproject.org/wiki/User:Toshio/Systemd_scriptlet_options however the end user himself must run systemd-sysv-convert --apply $service to apply it.
Created attachment 494778 [details]
Created attachment 494780 [details]
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
(In reply to comment #5)
> 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
Does this mean that any systemd compatibility mode issues that prevent things from working in a consistent way will be treated as blockers for F15?
Like this one https://bugzilla.redhat.com/show_bug.cgi?id=699835
So for f15, I should just put
SYSTEMCTL_SKIP_REDIRECT=1 ; export SYSTEMCTL_SKIP_REDIRECT
at the beginning of the regular sysv init script and save the other changes I've made for f16. Works for me.
Created attachment 521292 [details]
Created attachment 521293 [details]
aefc3ed..65e4166 master -> master
Author: Rich Megginson <firstname.lastname@example.org>
Date: Wed Apr 20 11:04:26 2011 -0600
Reviewed by: nhosoi (Thanks!)
Fix Description: Create a dirsrv-admin.service file for systemd and
allow it to use /etc/sysconfig/dirsrv-admin for its EnvironmentFile
When using systemd, have to use the systemctl start command in startServer
or other systemd commands like status, restart, stop will not work
Use systemctl to manage directory server instances too. The old service
support did not include the directory server too, so that was added.
Platforms tested: Fedora 16 x86_64
Flag Day: yes
Doc impact: yes
389-admin-1.1.24-1.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing 389-admin-1.1.24-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
389-admin-1.1.25-1.fc16 has been submitted as an update for Fedora 16.
389-admin-1.1.26-1.fc16 has been submitted as an update for Fedora 16.
389-admin-1.1.27-1.fc16 has been submitted as an update for Fedora 16.
389-admin-1.1.28-1.fc16 has been submitted as an update for Fedora 16.
389-admin-1.1.29-1.fc16 has been submitted as an update for Fedora 16.
389-admin-1.1.29-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Given that I have left the project and a new individual may or may not continue with systemd integration in the project by submitting new feature following whatever demands FPC and FESCo might have and thus new units in the process I'm closing this and all remaining bugs I had submitted for this particular feature as WONTFIX