Heads Up: FESCo is considering to block packages providing sysvinit services without systemd unit

["Jóhann B. Guðmundsson"]

On 11/14/2011 01:28 AM, Ian Kent wrote:
> Anyway, I'll start work on the logging changes and add a unit file and
> see how we go. Should autofs install the unit file into the systemd area
> or what should do?

So the final unit file should look something like this...

### autofs.service ###

[Unit]
Description=Automounts filesystems on demand
After=network.target ypbind.service

[Service]
Type=forking
PIDFile=/run/autofs.pid
EnvironmentFile=-/etc/sysconfig/autofs
ExecStart=/usr/sbin/automount ${OPTIONS} --pid-file /run/autofs.pid

[Install]
WantedBy=multi-user.target


You can find the packaging guidelines for systemd here

http://fedoraproject.org/wiki/Packaging:Systemd

Pay attention to the section that says drop the legacy sysv init script 
file or package it separately should it be shipped ( which makes no 
sense once a unit file is in place ) along with make sure that your unit 
file have correct file permissions.

Maintainers/Packagers shipping both the legacy sysv init script along 
with having incorrect file permissions on unit files ( for example 
auditd.service ip6tables.service iptables.service openvpn at .service 
wpa_supplicant.service that are part of default install come all with 
incorrect file permissons ( +x ) ).

The issue mention above seem to be the common mistakes/violations of the 
packaging guidelines when shipping native systemd units.

JBG