[systemd-devel] Starting CUPS very late on a desktop and non-server system

Michael Biebl mbiebl at gmail.com
Thu Feb 20 15:21:32 PST 2014


This might be of interest to you:
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2014-February/001433.html

So, the cups maintainer is already looking into this. It has to be
said CUPS is not the most trivial wrt proper systemd support.

2014-02-20 23:18 GMT+01:00 Paul Menzel <paulepanter at users.sourceforge.net>:
> Dear systemd folks,
>
>
> after Debian's CTTE chose systemd as the default init system for the
> next Debian release, I installed it on one of the systems.
>
> Looking at the output `systemd-analyze plot`, I noticed that CUPS takes
> 700 ms to start and as this is a desktop system where not a lot is
> printed and when, then only after the user has logged in, I wonder how
> that can be dealt with systemd. Like starting it only after user login?
> Or is that something which is not nicely doable because CUPS runs as a
> system daemon?
>
>
> Thanks,
>
> Paul
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


More information about the systemd-devel mailing list