ADJTIME_CONFIG(5)

๐Ÿ’– ADJTIME_CONFIG โ€” the whole vibe ๐Ÿ’–

okay so bestie, this is adjtime_config, aka the file format page from the adjtime_config(5) manual. it's all about your hardware clock's settings and drift factor. literally the little file that keeps your RTC in check. ๐Ÿ•ฐ๏ธโœจ


๐ŸŒธ NAME ๐ŸŒธ

adjtime_config โ€” all the tea about your hardware clock setting and its drift factor ๐Ÿ’…


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

/etc/adjtime

that's it. that's the whole thing. iconic. ๐Ÿ‘‘


โœจ DESCRIPTION โœจ

so the file /etc/adjtime holds descriptive info about the hardware mode clock setting and the clock drift factor. it gets read and written by hwclock(8), and it gets read by programs like rtcwake to figure out the RTC time mode. ๐Ÿซถ

normally it lives in /etc, but tools like hwclock(8) or rtcwake(8) can use a different location via command line options if you don't want write access to /etc. and if the file is just... missing? the default clock mode is "UTC". no biggie. ๐Ÿ’ซ

here's the thing though โ€” the Hardware Clock is usually not very accurate, bestie. ๐Ÿ˜ญ but the good news is that most of its inaccuracy is completely predictable โ€” it gains or loses the same amount of time every single day. that's what we call systematic drift. the util hwclock(8) keeps the file /etc/adjtime to hold onto some of that historical info. for more details, go read the "The Adjust Function" and "The Adjtime File" sections in the hwclock(8) man page. iykyk. ๐Ÿ“–

also the adjtime file is formatted in plain ASCII. old school, but it works. ๐Ÿงš

๐ŸŒˆ First line

three numbers, separated by blanks:

  • drift factor โ€” the systematic drift rate in seconds per day (floating point decimal)
  • last adjust time โ€” the resulting number of seconds since 1969 UTC of the most recent adjustment or calibration (decimal integer)
  • adjustment status โ€” zero (for compatibility with clock(8)) as a floating point decimal

๐Ÿฆ‹ Second line

  • last calibration time โ€” the resulting number of seconds since 1969 UTC of the most recent calibration. it's zero if there has been no calibration yet, or if it's known that any previous calibration is moot (for example, because the Hardware Clock has been found, since that calibration, not to contain a valid time). this one is a decimal integer. โญ

๐Ÿ“ Third line

  • clock mode โ€” supported values are UTC or LOCAL. it tells you whether the Hardware Clock is set to Coordinated Universal Time or local time. and you can always override this value with options on the hwclock(8) command line. you have the power, bestie. ๐Ÿ’ช๐Ÿ‘‘

๐Ÿ“ FILES ๐Ÿ“

  • /etc/adjtime

๐Ÿ‘€ SEE ALSO ๐Ÿ‘€

hwclock(8), rtcwake(8)


๐Ÿ™ˆ REPORTING BUGS ๐Ÿ™ˆ

found a bug? for bug reports, use the issue tracker at <https://github.com/util-linux/util-linux/issues>. don't be shy, they wanna know. ๐Ÿ›๐Ÿ’–


๐ŸŒŸ AVAILABILITY ๐ŸŒŸ

adjtime_config is part of the util-linux package, which you can download from the Linux Kernel Archive at <https://www.kernel.org/pub/linux/utils/util-linux/>. go get it. ๐Ÿซถ


and that's the whole page, bestie!! this was util-linux 2.42.4, dated 2026-09-21, for ADJTIME_CONFIG(5). mwah, slay, go forth and know your hardware clock ๐Ÿ’…๐ŸŽ€โœจ

๐Ÿ“ฆ where this page comes from
  • arch rolling: util-linux 2.42.4-1 ยท BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND LGPL-2.1-or-later AND LicenseRef-PublicDomain
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms