Am 14.04.2013 23:06, schrieb Kok: > On Sun, Apr 14, 2013 at 1:01 PM, Reindl Harald <h.rei...@thelounge.net> wrote: >> 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:
upstream seems to be dead maybe there are no bugs and development to improve things in this case upstream would not need to be more alive :-) but i doubt that is the truth and so maybe systemd can step into over the long........... >>>>> > [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 > <<<<< thanks, i will give it a try why not "Type=forking"? in my expierience a service works with simple/forking and only one of them while i must say my low-level understanding may not be enouh to realize what to use.............
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
