summaryrefslogtreecommitdiff
path: root/doc/s6-sntpclock.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/s6-sntpclock.html')
-rw-r--r--doc/s6-sntpclock.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/s6-sntpclock.html b/doc/s6-sntpclock.html
index e0fd0eb..823557c 100644
--- a/doc/s6-sntpclock.html
+++ b/doc/s6-sntpclock.html
@@ -6,14 +6,14 @@
<title>s6-networking: the s6-sntpclock program</title>
<meta name="Description" content="s6-networking: the s6-sntpclock program" />
<meta name="Keywords" content="s6-networking s6-sntpclock sntp clock sntpv4 client" />
- <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> -->
+ <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
</head>
<body>
<p>
<a href="index.html">s6-networking</a><br />
-<a href="http://skarnet.org/software/">Software</a><br />
-<a href="http://skarnet.org/">skarnet.org</a>
+<a href="//skarnet.org/software/">Software</a><br />
+<a href="//skarnet.org/">skarnet.org</a>
</p>
<h1> The <tt>s6-sntpclock</tt> program </h1>
@@ -87,7 +87,7 @@ then NTP just cannot compute. This is a problem for CMOS-less systems,
where the system clock is initialized to the Unix Epoch. The solution
is to first manually initialize the system clock with a program such as
<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html">date</a> or
-<a href="http://skarnet.org/software/s6-portable-utils/s6-clock.html">s6-clock</a>
+<a href="//skarnet.org/software/s6-portable-utils/s6-clock.html">s6-clock</a>
to a closer time (such as 2013-01-01, which will be good up to 2047), then
contact the NTP server. </li>
<li> A less obvious problem with NTP is that it works with UTC time,