Am 2011-08-23 08:27, schrieb Joost Roeleveld: > On Monday, August 22, 2011 11:09:02 PM Stefan G. Weichinger wrote: >> Am 22.08.2011 20:29, schrieb Stefan G. Weichinger: >>> update: edited the example in the gentoo-wiki now. >> >> replying to myself once more, which makes it feel more like a wiki >> or blog than a mailing-list ;-) > > There wasn't much to add. You provided a solution and the only reply > I could come up with "Well done" would sound condescending. Which is > why I decided not to.
ok, yes > I don't tend to use preload. Is it usefull in a non-systemd > environment? I always had the impression that things started faster with preload, yes. Might be less of an impact with the new SSD I have in my desktop machine now. I didn't really miss it when switching to systemd (where I don't have a service-file for it yet). >> http://en.gentoo-wiki.com/wiki/Improve_responsiveness_with_cgroups >> >> Is that stuff still valid? > > Maybe, if you want to group stuff you're running yourself into > seperate groups. The different services are grouped already. > >> With systemd the whole use of cgroups changes fundamentally, I >> don't have the knowledge to decide if to use both in parallel. >> >> For now I disabled the stuff from the wiki (stop sourcing >> /etc/bash/local/cgrouprc) as it only gives me warnings ... > > What kind of warnings? Systemd already mounts the filesystem for it > and starts poulating it. If your script does similar things, they > might try to duplicate work? The code tries to write to its own dir: mkdir -p -m 0700 $cdir/user/$$ > /dev/null 2>&1 /bin/echo $$ > $cdir/user/$$/tasks /bin/echo '1' > $cdir/user/$$/notify_on_release But somehow the mkdir seems to fail as I get warnings from the two echo-statements, that their "target-files" do not exist, which lead me to the fact that $cdir/user/$$ does not exist. > I think it is more useful on desktops and laptops, which get rebooted > regularly. On a server that tends to run for months without a > reboot, a fast init-system is important. You mean, "not so important" ? > And I don't really see the point of D-BUS on a server either. All the > services that need to talk to each other already have working > communication paths. > > I do intend to implement it on my desktop and netbook as I'd like to > have those booting as fast as possible. Yep, I agree. Stefan
