Created attachment 486834 [details] Native systemd service file Description of problem: The attached file is a native systemd file for upcoming F15 Feature [1] Please read [2] on how to packaging and installing systemd Service files. To learn more about Systemd daemon see [3]. To view old SysV with the new Systemd site by site see for your component see [4] If you have any question dont hesitate to ask them on this bug report. 1.http://fedoraproject.org/wiki/Features/systemd 2.https://fedoraproject.org/wiki/Systemd_Packaging_Draft 3.http://0pointer.de/public/systemd-man/daemon.html 4.https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 486842 [details] With After=syslog.target network.target Just noticed that I forgot to add after systlog.target and network target thus resubmitting..
why the network target ? Does it mean sssd startup will be delayed until the network is up ? Although sssd uses network resources it can handle a local db and it does handle offline operations by default including sensing on its own when the network is up in order to go online. So I am not sure it really needs to be configured to wwait for the network to be up. Also I se you have as After remote-fs.target too, why is that ?
I only added the remote.fs,target network.target ( and the local-fs,target ) because I thought there was a dependency issue due to this comment in the SysV init file ### BEGIN INIT INFO # Provides: sssd # Required-Start: $remote_fs <---??? Feel free to remove both network.target local-fs.target remote-fs.target if not needed. ( so the line should just be After=syslog.target ) You also might want to add Conflicts=nscd.service if necessary in the [Unit] section of the service file.
local-fs.target is never needed in systemd, since that is implied for normal services.
Created attachment 489051 [details] resubmitted without network.target local-fs.target remote-fs.target in After
Jakub, please take a look at this and if it's acceptable, please add this to source control and add a new configure flag to install this config file instead of the Sys V init script.
(In reply to comment #6) > Jakub, please take a look at this and if it's acceptable, please add this to > source control and add a new configure flag to install this config file instead > of the Sys V init script. Sure, the upstream ticket is https://fedorahosted.org/sssd/ticket/837
sssd-1.5.5-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/sssd-1.5.5-2.fc15
Package sssd-1.5.5-2.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.5.5-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/sssd-1.5.5-2.fc15 then log in and leave karma (feedback).
Package sssd-1.5.5-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.5.5-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/sssd-1.5.5-3.fc15 then log in and leave karma (feedback).
Package sssd-1.5.6-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.5.6-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/sssd-1.5.6-1.fc15 then log in and leave karma (feedback).
sssd-1.5.6-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
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