Write policy for starting/stopping/restarting systemd-readahead-drop.service

[ghost]

I saw one denial when stopping the service. I did not see any denials when restarting

type=USER_AVC msg=audit(1438547602.860:1925): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc:  denied  { stop } for auid=1000 uid=0 gid=0 path="/usr/lib/systemd/system/systemd-readahead-drop.service" cmdline="systemctl stop systemd-readahead-drop.service" scontext=toor_u:toor_r:toor_t:s0 tcontext=system_u:object_r:systemd_unit_file_t:s0 tclass=service  exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'

[mpalmi]

Resolved with Issue #134 in mpalmi@64322f0

[mpalmi]

readahead collect service appears inactive after boot
This seems to be due to the fact that we're running on a VM (ConditionVirtualization=no was not met).
We're probably going to want to test on hardware.

systemd-readahead-collect.service - Collect Read-Ahead Data
   Loaded: loaded (/usr/lib/systemd/system/systemd-readahead-collect.service; enabled)
   Active: inactive (dead)
           start condition failed at Sun 2015-08-02 20:34:59 GMT; 17s ago
           ConditionVirtualization=no was not met
     Docs: man:systemd-readahead-replay.service(8)

[ghost]

We will need to test this on hardware in the future