On Tue, Oct 16, 2012 at 9:19 AM, Joshua Collins <jeoshua@gmail.com> wrote:
On 10/16/12, Martín Cigorraga <msx@archlinux.us> wrote:
4. Is there any place for e4rat(lite)? Since I activated systemd's built-in ureadahead feature, will e4rat still add any improve- ment? What do you say?
I would suggest that you benchmark this for yourself. I found pretty good results using e4rat along with systemd readahead. It will end up taking quite a bit longer in "initrd" that way, but once it starts booting services end up taking a lot less time. A friend of mine, however, had bad results doing this, and found that Preload did a better job with Readahead and e4rat. He didn't have the benchmarks to back up his assertation tho.
That's was what I was looking for, thanks.
So ymmv, but make sure you're using some tool to benchmark the performance. What "feels" faster isn't always.
Totally, I will give'em a try then :) Regarding:
3. $ systemctl reboot and $ systemctl shutdown features: I feel a bit uncomfortable with the idea of having restricted users with the hability to reboot or shutdown the system, is there any way to change this so only r00t can issue these orders? (Without going dirty.)
Interesting, but I don't know. This may be a polkit setting. If you find out, I'd be interested. I was sugested in the #systemd channel that this may be associated with dbus: 06:31:17 Mithrandir | sounds like the dbus config isn't restrictive enough, you should get something like: 06:31:20 Mithrandir | > systemctl reboot 06:31:22 Mithrandir | Failed to issue method call: Access denied I'll keep you informed while I continue investigating this issue until I have enough info to file a bug.