Created attachment 492978 [details]
Native systemd service file for smolt
Description of problem:
I'm unsure if this is supposed to be a service file et all since it does not seem to be used by anything anyway...
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:
The only thing the init script is supposed to do (as far as I can tell) is to create /etc/smolt/hw-uuid if it doesn't exist. The lockfile is useless.
All it really needs to do is:
if [ ! -f /etc/smolt/hw-uuid ]; then
cat /proc/sys/kernel/random/uuid > /etc/smolt/hw-uuid
chmod 0644 /etc/smolt/hw-uuid
chown root.root /etc/smolt/hw-uuid
But I'm not really sure how to make a systemd unit that does that.
The monthly checkin itself is triggered by a cron job.
Created attachment 493326 [details]
New and improved version of smolt systemd service file..
Well technically since this is not an service daemon something else should create this like the application that offers the end user to enable monthly smolt updates but since systemd is so awesome and beefy let's do it.
The service vill refuse to run if /etc/smolt/hw-uuid does exit and once it has run it will disable itself encase something enabled it as a good run once service should do..
I think a nice solution would be to use /etc/machine-id instead of a uuid of its own for identifying the machine. For more details see http://0pointer.de/blog/projects/the-new-configuration-files.html
The cron job is triggered by the existence of the /etc/smolt/hw-uuid and the only thing that this so called service does is to create that file.
Why this is an sysv init script beats the hell out of me ( as opposed to be something like smolt --enable-monthly cmd that either get run by user of by something else like firstboot )
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
What's the current status on this?
Please follow the following guidelines to package the service correctly.
Will what's the hold up ?
1.4.3-4 removed the pointless initscript and 1.4.3-5.fc16 is stable now.