On Sun, Apr 14, 2013 at 1:01 PM, Reindl Harald <h.rei...@thelounge.net> wrote: > > Am 14.04.2013 21:18, schrieb Kok: >> On Sun, Apr 14, 2013 at 12:05 PM, Reindl Harald <h.rei...@thelounge.net> >> wrote: >>> what about a dbus-triggered instance like cups and other services >>> are fired up after login which creates a /.readahead-usersession >>> proceeded at boot the same way as /.readahead >> >> it does more damage to do excessive readahead at boot for services >> that don't need to start until way, way after boot. The whole idea is >> to only read things you are going to need, and not more. Otherwise you >> could just read everything you can possibly read from disk into >> memory > > oh, now i realized that systemd-readahead covers any file-type > surely it would be bad preloading anything including data > > please have a look at > http://koji.fedoraproject.org/koji/buildinfo?buildID=393183 > this is covering only libraries but seems to be in a bad maintaining-state > because still no systemd-unit and all of te last updates where auto > mass-rebuilds > > i wrote a systemd-unit for my machine which starts after kdm.service > https://bugzilla.redhat.com/show_bug.cgi?id=951956
that unit file should just go into the project upstream, I'd also suggest removing the kdm dependency, running with -f, making log output go to stdout and removing the Type=forking, so it becomes: >>>> [Unit] Description=Adaptive readahead daemon [Service] ExecStart=/usr/sbin/preload -f 1 -l "" Restart=always RestartSec=1 Nice=19 IOSchedulingClass=3 [Install] WantedBy=multi-user.target <<<<< _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel