[aklug] Re: systemd pushback

I really like systemd.. but not as a desktop user yet.

As a web and database developer I have a lot of appreciation for event
driven init services that can keep services alive as part of their core
process as well as take on some security and chain-of-event processing that
helps let everything fall in to place.

I use automation software like Salt to do a lot of things... but it falls
down in a few areas concerning early boot scenarios. Systemd is helping me
a lot with encrypted volume support and launching a myriad of services with
specific command line arguments after volumes are mounted. Take for
instance MongoDB. You actually have lots of different daemons that can be
used to help deal with clusters.. the sharding daemon, the config daemon,
and the database handler daemon. Two of these share the same binary. I
can either fudge up an initscript to deal with this OR I can do some simple
declarations with systemd.

There is a bit of supervision fluff that is not built in.. but it does
simple process supervision well enough.

One thing I am dying to eventually have working and tested is per user
systemd configurations.

On Mon, Apr 28, 2014 at 8:15 AM, <bryanm@acsalaska.net> wrote:

> This web page offers a list of grievances regarding systemd, which
> is apparently replacing the init system in lots of Linux distributions
> these days:
>
> http://boycottsystemd.org/
>
> I hadn't been paying much attention to systemd, but based on these
> complaints, it may deserve some serious worry and/or action. Patrick
> Volkerding, the Slackware leader, posted a link to the page with the
> comment "When I realized I wasn't reading the Onion, I cried into my
> morning coffee.".
>
> --
> Bryan Medsker
> bryanm@acsalaska.net
>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Thu May 1 15:59:31 2014