NTPWAIT(8)
π NTPWAIT π
okay bestie, so you know ntpwait(8) from the NTPsec crew? yeah, that one. this is the little boot-time bouncer that stands there with its arms crossed until your clock gets its life together. let's get into it π«Ά
β¨ NAME β¨
ntpwait β wait for ntpd to stabilize the system clock. she just waits. that's the whole job. and she EATS at it π
β¨ SYNOPSIS β¨
ntpwait [-vV] [-n number] [-s secs]
β¨ DESCRIPTION β¨
so here's the tea, bestie: the ntpwait program blocks until ntpd is in synchronized state. like, it will literally just sit there. no cap. it does not move on until the clock is behaving.
and why would you want that? boot time, babes. this is the move when you want to delay the boot sequence until after ntpd -g has set the time. iconic behavior honestly, very "we do not proceed until the vibes are correct" of you.
here's the mechanics: ntpwait will send at most number queries to ntpd(8), and it sleeps for secs seconds after each status return that says ntpd(8) has not yet produced a synchronized and stable system clock. so it checks, sleeps, checks, sleeps β a little rhythm, a little routine. it's giving patient queen. π
and she does all of this quietly, unless the -v flag is provided. no chatter by default. silent but locked in.
β¨ OPTIONS β¨
-n number,--tries=numberβ Number of times to checkntpd. This option takes an integer number as its argument. The default number for this option is:100.
read that again: this is the max number of times we will check ntpd to see if it has been able to synchronize and stabilize the system clock. a hundred tries, bestie. she is nothing if not committed. π
-s secs-between-tries,--sleep=secs-between-triesβ How long to sleep between tries. This option takes an integer number as its argument. The defaultsecs-between-triesfor this option is:6.
we will sleep for secs-between-tries after each query of ntpd that returns "the time is not yet stable". so it's a lil nap between vibe checks. six seconds of beauty rest by default. π΄
-v,--verboseβ Be verbose.
By default, ntpwait is silent. With this option, ntpwait will provide status information, including time to synchronization in seconds. so if you're nosy (affectionate) this is your girl. she'll tell you exactly how it's going and how long till the clock is ready. π
-V,--versionβ Print the version string and exit.
short and sweet. she says her version and dips. βοΈ
β¨ BUGS β¨
okay so there's ONE little thing and it's giving "old tech problems": if you are running Python at a version older than 3.3, the report on time to synchronization may be thrown off by NTP clock stepping. so like, the number she gives you about time-to-sync might be lying a little. not her fault. blame the Python. π
β¨ EXIT STATUS β¨
One of the following exit values will be returned:
0β Successful program execution. she did it. slay. π1β The operation failed or the command syntax was not valid. something went wrong, or you typed it weird. π2β Operation was interrupted by signal. someone hit her with a signal mid-wait. rude, but okay. β‘
πΈ SEE ALSO πΈ
...okay so the original page doesn't actually give us a SEE ALSO section, so there's nothing to list here. we respect the canon. π€·ββοΈ
and that's the whole page, bestie!! go forth and wait for your clock to stabilize, you absolute main character. π
sign-off: this whole vibe came from NTPsec, dated 2026-10-21, page NTPWAIT(8). mwah. π
π¦ where this page comes from
- fedora 43: ntpsec 1.2.6-1.fc43 Β· NTP AND BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause AND ISC AND Apache-2.0 AND Beerware
- fedora 43: ntpsec 1.2.6-1.fc43 Β· NTP AND BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause AND ISC AND Apache-2.0 AND Beerware
- fedora 44: ntpsec 1.2.6-1.fc44 Β· NTP AND BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause AND ISC AND Apache-2.0 AND Beerware
- fedora 44: ntpsec 1.2.6-1.fc44 Β· NTP AND BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause AND ISC AND Apache-2.0 AND Beerware
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms