Re: A few observations about systemd
]] Russell Coker
| On Tue, 19 Jul 2011, Bastien ROUCARIES <firstname.lastname@example.org> wrote:
| > > The above is from the ps output of one of my i386 servers running
| > > Squeeze. It appears that systemd has allocated an extra 2324K of RAM
| > > and has an extra 2712K resident. Given that it's difficult to buy a
| > > phone with less than 256M of RAM nowadays that doesn't seem to be a big
| > > problem, and systemd can save memory by removing the need to run other
| > > daemons.
| > I have some avr32 card with 32Mb that are valuable and do measurement
| > over network with blas/lapack. 1Mb is a lot of double. Phone is not
| > the only market.
| How do dpkg and apt-get run on that?
A noop apt-get update takes about 10.5s, one where it updates most of
the Packages files is at closer to six minutes. This is with / on a SD
card and no swap.
| > pid == 1 is immortal. I should not get unrecoverable signal like
| > sigsegv. I could restart other daemon if needed.
| Jul 19 01:01:47 unstable64 systemd: Caught <SEGV>, dumped core as pid 889.
| Jul 19 01:01:47 unstable64 systemd: Freezing execution
| It's not strictly unrecoverable. If you run "kill -11 1" then you get the
| above in syslog.
| But it does result in a system that doesn't work properly.
Well, yes. If init crashes, stuff generally don't work that well
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are