Bug #16965

Check if our CUPS systemd service/socket tweaks still work and are still needed

Added by intrigeri 2019-08-10 08:52:51 . Updated 2019-08-10 12:14:43 .

Status:
Resolved
Priority:
Elevated
Assignee:
intrigeri
Category:
Persistence
Target version:
Tails_4.0
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

In config/chroot_local-hooks/52-update-rc.d we disable cups.service and enable cups.socket. There’s a comment that explains why but last time we checked this was in the Tails 2.x era.

Let’s:

  • Verify that “cupsd is started during the initialization of the GNOME session, which is fine: by then, the persistent /etc/cups has been mounted” is still true on Buster.
  • Check whether we still need to do this at all, i.e. whether CUPS in Buster still enables the service, and not the socket activated one, by default.

Subtasks

Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 2019-08-10 08:53:11

#2 Updated by intrigeri 2019-08-10 12:13:44

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri

intrigeri wrote:
> * Verify that “cupsd is started during the initialization of the GNOME session, which is fine: by then, the persistent /etc/cups has been mounted” is still true on Buster.

Still true.

> * Check whether we still need to do this at all, i.e. whether CUPS in Buster still enables the service, and not the socket activated one, by default.

By default, it will enable cups.{service,path,socket}. So our code effectively disables cups.{path,service} and leaves cups.socket enabled:

Executing: /lib/systemd/systemd-sysv-install disable cups
Removed /etc/systemd/system/printer.target.wants/cups.service.
Removed /etc/systemd/system/sockets.target.wants/cups.socket.
Removed /etc/systemd/system/multi-user.target.wants/cups.path.
Created symlink /etc/systemd/system/sockets.target.wants/cups.socket → /lib/systemd/system/cups.socket.

#3 Updated by intrigeri 2019-08-10 12:14:43

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|6c496a80b0b36cafc8236ebf00f39f91d105e00a.