Fedora, systemd, and changes

Posted Jun 16, 2011 15:29 UTC (Thu) by vonbrand (subscriber, #4458)
In reply to: Fedora, systemd, and changes by cdmiller
Parent article: Fedora, systemd, and changes

I'm sorry, but the whole point of init is managing the whole show. And the "simple, stable" init we are accustomed to by now just doesn't cut it. The huge mess of repetitive scripts, which can't do much more than try to start the service and hope for the best because the dependency information just isn't available worked (sort of) in relatively stable environments with an experienced sysadmin on hand to iron out the inevitable wrinkles. That world might linger on in the datacenter, but to really get elsewhere a fundamental reachitecting is overdue. I believe systemd is that (or a large step in the right direction).

OTOH, when my netbook has 2GiB RAM, a few dozen MiB "wasted" is not that big a deal.

Fedora, systemd, and changes

Posted Jun 16, 2011 20:45 UTC (Thu) by jond (subscriber, #37669) [Link] (4 responses)

Sure, but when VPS can often start with as little as 64M of RAM

Fedora, systemd, and changes

Posted Jun 18, 2011 22:18 UTC (Sat) by elanthis (guest, #6227) [Link] (3 responses)

What exactly do you _do_ with a VPS that only has 64MB of RAM, other than brag about having done so? (Seriously, I'm curious.)

Fedora, systemd, and changes

Posted Jun 20, 2011 3:12 UTC (Mon) by ThinkRob (guest, #64513) [Link] (2 responses)

I've got one, so I'll chime in: SSH server, VPN box, personal/friends/family www server, FTP server for off-site backups, other misc tasks. (The last one usually starts with something like "I need a way to see if $X is available/has an open port/responds to ping every $Y minutes..." and ends with a shell script and a new crontab entry.)

Could I afford a VPS with 128 MB? Yes. Do I want to pay my provider another few bucks a month just because the development world takes the attitude of "everyone can spare a few more MB for *my* app"? No.

Fedora, systemd, and changes

Posted Jun 20, 2011 19:13 UTC (Mon) by intgr (guest, #39733) [Link] (1 responses)

> I've got one, so I'll chime in: SSH server, VPN box, personal/friends
> /family www server, FTP server for off-site backups, other misc tasks

Great news then, systemd revives the long lost Unix socket activation technique. Your daemons don't have to stick around all the time, wasting memory even when nobody is connected, but are only launched when necessary.

When the SELinux bug gets crushed, your system will end up using *less* memory with systemd. :)

Fedora, systemd, and changes

Posted Jun 20, 2011 22:51 UTC (Mon) by mathstuf (subscriber, #69389) [Link]

> When the SELinux bug gets crushed, your system will end up using *less* memory with systemd. :)

I can attest to this. My x86_64 SELinux-disabled Rawhide desktop boots with ~160MB of RAM used. With F14, it used at least 350MB. Of course, my 32bit installs similar to the F14 setup booted with less than 90MB used (and rebooted in < 45s on a 900MHz Atom). Still not sure what was causing the huge discrepancy between 32 and 64 bit.