From 5e810f82fd36d606f48d9a1218d2b8937bdf04ef Mon Sep 17 00:00:00 2001
From: Mark Reynolds <mreynolds@redhat.com>
Date: Jul 26 2016 21:00:11 +0000
Subject: Ticket 48935 - Update dirsrv.systemd file


BUg Description:  Two issues here.  First the default system startup timeout
                  is set to 1 minute 30 seconds.  But in the start-dirsrv script
                  it attempts to use a 10 minute timeout.

                  Second, starting in F23 systemd does not work well with valgrind.
                  systemd does not accept the notification once the DS starts.
                  So the start command actually fails after it times out.

Fix Description:  For the first issue set the system startup timeout to match the
                  start-dirsrv script by setting:

                        TimeoutStartSecs=10min

                  Second, allow valgrind's startup success message to be
                  recognized/accepted we set:

                        NotifyAccess=all

https://fedorahosted.org/389/ticket/48935

Reviewed by: nhosoi(Thanks!)

(cherry picked from commit ce44176803aa52ab8001113136bfbb7ff4a50972)

---

diff --git a/wrappers/systemd.template.sysconfig b/wrappers/systemd.template.sysconfig
index d88bdcd..e653c86 100644
--- a/wrappers/systemd.template.sysconfig
+++ b/wrappers/systemd.template.sysconfig
@@ -1,3 +1,6 @@
 [Service]
+TimeoutStartSec=10m
+NotifyAccess=all
+
 # uncomment this line to raise the file descriptor limit
 # LimitNOFILE=8192