Armin K. wrote:
> On 02/10/2014 02:50 PM, Igor Živković wrote:

> The actual problem is logind, which can't be run without systemd since
> version 205+ due to change in cgroups handling, and that's rather a
> kernel requirement, not really enforced by systemd.
>
> The bigger problem than that is that there's no good replacement for
> logind at the moment. ConsoleKit is dead, insecure and doesn't have
> everything that people require nowadays.
>
>> * Setting up for API lock-in (having the DBus interfaces provided by
>> systemd become a necessary API that user-level programs depend on).
>
> Using D-Bus API's instead of C/C++ API's makes the code more portable.
> Several different projects can export same D-Bus API's and you can use
> them without the need to port over. Rare case, but it's possible (see
> notification daemon or policykit agent interfaces - same interfaces
> exported by several different packages).
>
> systemd also provides C API's so it's just systemd that really requires
> D-Bus now and will require kdbus later.

Why does systemd need D-Bus?  Because they pulled in login?  That's 
seems to be a circular argument to me.

If you are creating a server with Apache, php, and mariadb or mysql, 
where the only access is via a web browser or ssh, why do you need D-Bus 
at all?

As an example, anduin has been up 399 days and does not use D-Bus at 
all.  Here is the entire list of unique running processes:

anvil
/bin/sh /usr/bin/mysqld_safe
klogd
pickup -l -t fifo -u
qmgr -l -t fifo -u
/sbin/agetty tty1 9600
/sbin/udevd --daemon
smtpd
syslogd
/usr/bin/python /srv/mailman/bin/mailmanctl
/usr/bin/python /srv/mailman/bin/qrunner
/usr/bin/rsync --daemon
/usr/lib/postfix/master
/usr/lib/sa/sadc
/usr/sbin/fcron
/usr/sbin/httpd
/usr/sbin/mysqld
/usr/sbin/ntpd
/usr/sbin/sshd
/usr/sbin/vsftpd

What advantages would systemd give?  I can tell you the disadvantages: 
less control of what is running.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to