The RPM Fusion OpenAFS client and server packages in Fedora 18 now use
native systemd unit files. If you use OpenAFS from RPM Fusion and you
are upgrading from a previous Fedora release like Fedora 16 or 17,
please be aware of a few things.
1) Previously the /etc/init.d/openafs script controlled both the
server and client. This is now split into two unit files:
openafs-client and openafs-server. Users can stop and start each
2) If you have set OpenAFS to start on boot on an earlier version of
Fedora, and you upgrade to Fedora 18, OpenAFS will no longer start on
boot. You will need to run:
systemctl enable openafs-client.service
and if you also host an AFS bosserver:
systemctl enable openafs-server.service
This is roughly equivalent to the old-style SysV:
chkconfig openafs on
3) I've had to make some backwards-incompatible changes to the
openafs sysconfig file. If you are upgrading from a previous Fedora
1) Backup your current /etc/sysconfig/openafs
2) Move /etc/sysconfig/openafs.rpmnew to /etc/sysconfig/openafs
3) Re-apply any local changes you'd made.
Lastly, Fedora 17 (and ELRepo 5 & 6) will still use the SysV init
script. This change only affects Fedora 18 and above.
Show replies by date