systemd (Was Re: tmpfs for strategic directories)

Lennart Poettering mzerqung at
Tue May 25 19:07:37 UTC 2010

On Tue, 25.05.10 20:38, Alexander Boström (abo at wrote:

> tis 2010-05-25 klockan 20:30 +0200 skrev Lennart Poettering:
> > /etc/systemd/system. We could for example choose to not have that
> > symlink by default, but ask the administrator to create it if he sets up
> > a multiplexing print server the way Tim suggested.
> Wouldn't it be started automatically anyway when something connects to
> systemd's *:631 socket?

Yes, absolutely.

Tim's point originally was about two things:

1) what if browsing for daemons takes a long time and hence starting
   cupsd only when somebody opens the print dialog might not 
   make some people happy if the print dialog is only populated with
   printers after a minute of searching or so. I personally believe that
   this is a problem of the browsing protocol, as mDNS/DNS-SD does not
   suffer by problems like this and should provide the list of printers
   in under a second in any case. (browsing protocols should probably
   query the network for printers only when somebody actually want to see the
   data and not alraedy in advance like cups native browsing protocol is
   currently doing, simply to minimize the traffic this

2) What happens if a print server is merely a "router" for print jobs,
   and exclusively publishes *non-local* printers on the network for
   browsing. That machine wouldn't have any local printer then and starting the cups
   daemon on-demand would not suffice since the machine would have to
   announce the printer on the network first.


Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net           GnuPG 0x1A015CC4

More information about the devel mailing list