Date: Sun, 20 Mar 2022 14:36:29 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jordan@jwillikers.com, pgsql-docs@lists.postgresql.org
Subject: Re: systemd service start - disable timeout with "infinity"
Message-ID: <20220320193629.GW28503@telsasoft.com>
References: <164770078557.670.5467111518383664377@wrigleys.postgresql.org>
 <1445301.1647792679@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1445301.1647792679@sss.pgh.pa.us>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20220320193629.GW28503%40telsasoft.com>
Precedence: bulk

On Sun, Mar 20, 2022 at 12:11:19PM -0400, Tom Lane wrote:
> PG Doc comments form <noreply@postgresql.org> writes:
> > In the service start section of the documentation, it is stated that using a
> > value of zero for TimeoutSec disables the systemd timeout. This is not
> > accurate and according to the documentation of systemd,
> > https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStartSec=,
> > this should be set to "infinity" to disable the timeout.
> 
> Hmm ... maybe zero works too, or worked when this was written?
> But you're right that "infinity" is now the documented way
> to do it.  Will fix, thanks for the report.

FYI
https://www.postgresql.org/message-id/flat/20211129220234.GQ17618%40telsasoft.com
https://git.postgresql.org/gitweb/?p=pgrpms.git&a=commitdiff&h=c74dbe3781478597712066354d19b754ba4b7683
+# 0 is the same as infinity, but "infinity" needs systemd 229
+TimeoutStartSec=0