[HEADS-UP] The systemd unit files I'll post

[Lennart Poettering]

On Thu, 15.07.10 11:04, Tim Waugh (twaugh at redhat.com) wrote:

> Another question about the cups config:
> 
> [Install]
> # This is activated via any of these three triggers:
> # 1. Somebody connects to its sockets
> # 2. A file is in the spool directory
> # 3. A printer is plugged in
> # This follows the same scheme MacOS uses to spawn CUPS only when necessary
> Also=cups.socket cups.path
> WantedBy=printer.target
> 
> I think I mentioned in the original systemd discussion that there is a
> case not covered by this approach, which is that there is a network
> queue configured and available to the network, i.e. this computer is a
> central print server for a bunch of network printers.
> 
> In this case, there is no local requirement for cups to be running --
> the requirement is that the service is available to the network.
> 
> Will it be possible/easy for administrators to configure that?

Yes, trivial almost. If people want to enable a service by default on
boot they can place a single symlinks:

# ln -sf /lib/systemd/system/cups.service /etc/systemd/system/multi-user.target.wants/cups.service

There's even a FAQ for that now:

http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions

Lennart

-- 
Lennart Poettering - Red Hat, Inc.