From: Zdenek Dohnal <zdohnal@redhat.com>
Date: Wed, 25 Nov 2020 08:31:31 +0000 (+0100)
Subject: [Fedora] cups.service.in: Start cupsd after NIS is started
X-Git-Tag: v2.3.3op1~7^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bcbb5582e9d6e9fd6b557786662b56c2d6292087;p=thirdparty%2Fcups.git

[Fedora] cups.service.in: Start cupsd after NIS is started

If an user has a NIS group as SystemGroup in cups-files.conf, then cupsd fails to start if it is activated before ypbind service. Setting 'After=ypbind.service' sets unit's order to cupsd being started after ypbind.

Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1494558
---

diff --git a/scheduler/cups.service.in b/scheduler/cups.service.in
index 9609d8ee7f..9e70b29731 100644
--- a/scheduler/cups.service.in
+++ b/scheduler/cups.service.in
@@ -1,7 +1,7 @@
 [Unit]
 Description=CUPS Scheduler
 Documentation=man:cupsd(8)
-After=network.target sssd.service
+After=network.target sssd.service ypbind.service
 Requires=cups.socket
 
 [Service]