2018-10-18 06:00:45 +00:00
committed by Git OBS Bridge
parent adac94ced2
commit 9f1b32331c
2 changed files with 4 additions and 4 deletions

View File

@@ -62,7 +62,7 @@ Patch10: cups-2.1.0-choose-uri-template.patch
Patch11: cups-2.1.0-default-webcontent-path.patch
# Patch12 cups-2.1.0-cups-systemd-socket.patch Use systemd socket activation properly:
Patch12: cups-2.1.0-cups-systemd-socket.patch
# Patch42 Let cuspd start after possible network connection (boo#1111351)
# Patch42 Let cupsd start after possible network connection (boo#1111351)
Patch42: let-cupsd-start-after-network.patch
# Patch100...Patch999 is for private patches from SUSE which are not intended for upstream:
# Patch100 cups-pam.diff adds conf/pam.suse regarding support for PAM for SUSE:
@@ -316,7 +316,7 @@ printer drivers for CUPS.
%patch11 -b default-webcontent-path.orig
# Patch12 cups-2.1.0-cups-systemd-socket.patch Use systemd socket activation properly:
#patch12 -b cups-systemd-socket.orig
# Patch42 Let cuspd start after possible network connection (boo#1111351)
# Patch42 Let cupsd start after possible network connection (boo#1111351)
%patch42 -p0
# Patch100...Patch999 is for private patches from SUSE which are not intended for upstream:
# Patch100 cups-pam.diff adds conf/pam.suse regarding support for PAM for SUSE:

View File

@@ -1,11 +1,11 @@
From: Werner Fink <werner@ssue.de>
Date: Thu, 18 Oct 2018 05:32:42 +0000
Subject: Let cuspd start after possible network connection
Subject: Let cupsd start after possible network connection
For remote printer and printer servers, let cupsd always
start after a possible network connection. This let cupsd
also stop before a used network connection goes down, hence
the cusp does not lock due waiting on remote printers.
the cups does not lock due waiting on remote printers.
---
scheduler/org.cups.cupsd.service.in | 1 +