Re: systemd service start - disable timeout with "infinity"
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: jordan@jwillikers.com, pgsql-docs@lists.postgresql.org
Date: 2022-03-20T19:45:09Z
Lists: pgsql-docs
Justin Pryzby <pryzby@telsasoft.com> writes: > On Sun, Mar 20, 2022 at 12:11:19PM -0400, Tom Lane wrote: >> 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. > +# 0 is the same as infinity, but "infinity" needs systemd 229 Ah, thanks for the data point. 229 is far enough back that I'm not too troubled about that; besides, since this is just a documentation example, clarity is more important. BTW, what I read in the systemd docs is that TimeoutSec is a shorthand for setting both TimeoutStartSec and TimeoutStopSec, so the code in our RPMs looks a bit dubious now: # Do not set any timeout value, so that systemd will not kill postmaster # during crash recovery. TimeoutSec=0 +# 0 is the same as infinity, but "infinity" needs systemd 229 +TimeoutStartSec=0 + +TimeoutStopSec=1h + [Install] This is making assumptions about what order the values are applied in, plus the initial comment is no longer very accurate. regards, tom lane
Commits
-
Doc: fix our example systemd script.
- 0de9b999d14f 10.21 landed
- f693e9964010 11.16 landed
- 88418aacc9ff 12.11 landed
- 36c3acb397e1 13.7 landed
- a1efc8f8c820 14.3 landed
- 3f513ac7935d 15.0 landed