[arch-general] When will Arch switch to Systemd

[Sander Jansen]

On Thu, Jan 20, 2011 at 8:07 PM, Heiko Baums <lists at baums-on-web.de> wrote:
> Am Fri, 21 Jan 2011 09:03:23 +0800
> schrieb Ng Oon-Ee <ngoonee at gmail.com>:
>
>> This talk is probably a year or so out of date however. Try pulseaudio
>> now, I think you'll be pleasantly surprised. You'd also have noticed
>> that actual bug reports on our forums/ML etc. concerning pulseaudio
>> have dropped to close to nil.
>
>
> 5. In the same article I read that systemd binds itself to port 80
> instead of starting apache at boottime and starts apache only if a
> request to port 80 comes in. This is not the task of an init system, and
> I have slight security concerns about that. If I tell the init system
> that I want apache being started then I want to have apache started at
> boottime or when I say so and not when systemd thinks it is needed.
> And this way systemd first needs to unbind itself from port 80 and then
> start apache and bind it to port 80. So if I open port 80 in my firewall
> this port is open without a software being bound to it, even if it's
> only a millisecond.
>

The same article also mentions this is hardly a new concept. inetd has
been capable and doing this for years. And guess what, you can
actually configure the desired behaviour. For example there are
currently two different unit files for sshd. One that just starts the
daemon, while the other one will only start if there's a incoming
connection.

https://github.com/falconindy/systemd-arch-units/blob/master/service/sshd.service
vs
https://github.com/falconindy/systemd-arch-units/blob/master/service/sshd%40.service

Cheers,

Sander