aboutsummaryrefslogtreecommitdiff
path: root/guix.scm
diff options
context:
space:
mode:
authorGuillaume Le Vaillant <glv@posteo.net>2024-11-20 13:28:33 +0100
committerGuillaume Le Vaillant <glv@posteo.net>2024-11-20 15:10:04 +0100
commit0c386075244566748618734e9b5073059f598f89 (patch)
treec69398bd3c9a0ebef1ad515b05fbf09aa2207abd /guix.scm
parent72ef08da9d4cd811d59be95bebc0ea8492427587 (diff)
downloadguix-0c386075244566748618734e9b5073059f598f89.tar.gz
guix-0c386075244566748618734e9b5073059f598f89.zip
gnu: cl-in-memory-streams: Update to 2.0-1.a081214.
* gnu/packages/lisp-xyz.scm (sbcl-in-memory-streams): Update to 2.0-1.a081214. [inputs]: Add sbcl-bordeaux-threads. Change-Id: I6c69a64469e67e2337da343d462091d141c1277b
Diffstat (limited to 'guix.scm')
0 files changed, 0 insertions, 0 deletions
resh to 12h.Felix Lechner The Knot DNS service in Guix uses two days, or 48 hours, for the SOA refresh interval but that is outside the range of RFC 1912, which is entitled "Common DNS Operational and Configuration Errors." [1] Section 2.2 of RFC 1912 recommends a maximum of 12 hours for the SOA refresh rate: "You can keep it short (20 mins to 2 hours) if you aren't worried about a small increase in bandwidth used, or longer (2-12 hours) if your Internet connection is slow or is started on demand." This commit sets the default refresh interval at the nearest value recommended by the standard, which is 12 hours. Due to the widespread adoption of NOTIFY messages between primary and secondary DNS servers, the SOA refresh interval has arguably lost some importance, but the Guix default should still be in line with the standards. Values outside the recommended range can provoke warning messages from services commonly used to find bugs in DNS configurations, such as the MX Toolbox Super Tool. [2] [1] https://datatracker.ietf.org/doc/rfc1912/ [2] https://mxtoolbox.com/SuperTool.aspx * gnu/services/dns.scm (<zone-file>)[refresh]: Default to (* 12 3600). Signed-off-by: 宋文武 <iyzsong@member.fsf.org>