On 2014-06-05 20:20, Anton Aylward wrote:
On 06/05/2014 11:32 AM, Carlos E. R. wrote:
programs to do. Systemd is NOT monolithic any more than the BASH
shell is monolithic. The original shell of the V7 era was minimalist and the And systemd is not a single big binary, it is divided in several modules. I don't know how many.
|> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND |> root 1 0.0 0.0 197828 5020 ? Ss May24 0:22 /sbin/init
Perhaps you should consider a few other things that are shown there.
...
The second thing of note is because systemd is really a dispatcher, and one that does most of its work at the start of things (boot being one of those 'things') it is not consuming much cpu.
Once I had the old init consuming... I don't remember, maybe 90% CPU. It was outrageous and absurd. Well, the cause was that my modem had got into an unknown state, an internal loop or something, maybe sending repeated irq signals via serial port (I did not find out what), but "init" was attending to the modem signals full time with all the cpu power available. A power cycle of the modem solved the issue - but before finding the culprit, I did reboot Linux, to no use. It kept me mad for hours. The old inittab file had lines for attending to the modem, triggered from PID 1. Either for console and remote access, or for fax. But I don't think I was using that feature that instant. ...
Compared to the resident parts of firefox and thunderbird items such as systemd and BASH are insignificant.
Indeed :-) Yesterday, my firefox was using 2 gigs RES. (!).
If you want to make improvements or fret about consumption then there are areas where effort will have more effect than getting a later over systemd.
Perhaps you didn't notice I was being ironic? ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)