Red Hat Bugzilla – Bug 697664
Providing native systemd file for upcoming F15 Feature Systemd
Last modified: 2011-07-05 07:26:02 EDT
Created attachment 493019 [details]
Native systemd service file for pppoe-server
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:
Note that this service file might need different Type= ( Type=forking or Type=oneshot + RemainAfterExit=yes ) than the default I was unable to test this since the old sysv failed to start.
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
Looking for status update on this and btw just out of curiosity is this service applicant for hardware activation unfortunately our guidelines are a bit short on how to do that
Hardware activation occurs when a service is installed but only turns on if a
certain type of hardware is installed. Enabling of the service is normally done
with a udev rule. At this time we do not have further guidance on how to write
those udev rules. The service itself installs its .service files in the normal
places and are installed by the normal systemd scriptlets. These services
should never be enabled by the package as they will be enabled by udev. "
But you can read man systemd.device and look at the bluetooth service which is
doing that I believe..
it's fixed in rp-pppoe-3.10-9.fc16