From ce630033523e7a6492dcfde82edae9e89818f84e Mon Sep 17 00:00:00 2001
From: Pat Riehecky <riehecky@fnal.gov>
Date: Fri, 27 Dec 2019 13:33:42 -0600
Subject: [PATCH] Delay gssproxy start until after network.target

Systemd docs are unclear in this regard, but it appears that
network.target must be ready before domain sockets can be created.

Signed-off-by: Pat Riehecky <riehecky@fnal.gov>
[rharwood@redhat.com: rewrote commit message]
Reviewed-by: Robbie Harwood <rharwood@redhat.com>
Merges: #252
(cherry picked from commit 153b2ed51c5059abee507ddd240b5abc288d722c)
(cherry picked from commit 004ac514cd238122b25e5bc5b493dc8d4964ad75)
---
 systemd/gssproxy.service.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/systemd/gssproxy.service.in b/systemd/gssproxy.service.in
index ac37df6..50aafd7 100644
--- a/systemd/gssproxy.service.in
+++ b/systemd/gssproxy.service.in
@@ -1,7 +1,7 @@
 [Unit]
 Description=GSSAPI Proxy Daemon
 # GSSPROXY will not be started until syslog is
-After=syslog.target
+After=syslog.target network.target
 Before=rpc-gssd.service
 
 [Service]