WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/sys?h=master 2021-03-09T15:08:23Z 2021-03-09T15:08:23Z bluhm bluhm@openbsd.org 2021-03-09T15:08:23Z urn:sha1:5fc6fc53eed51b106058ed08dbfbec744f12aebd are started before syslogd(8). This resulted in ugly sendsyslog(2) dropped logs and the real message was lost. Create a temporary stash for log messages within the kernel. It has a limited size of 100 messages, and each message is truncated to 8192 bytes. When the stash is exhausted, the well-known dropped message is generated with a counter. After syslogd(8) has setup everything, it sends a debug line through libc to flush the kernel stash. Then syslogd receives all messages from the kernel before the usual logs. OK deraadt@ visa@ 2021-03-02T17:43:04Z deraadt deraadt@openbsd.org 2021-03-02T17:43:04Z urn:sha1:fd874303f21d95e37c4b1c2e7e2d403ce351bd90 2021-02-04T18:51:01Z bluhm bluhm@openbsd.org 2021-02-04T18:51:01Z urn:sha1:25c653a31002f33b0f9f406fd0ae4377b1a9959a OK claudio@ visa@ 2021-01-20T19:44:48Z otto otto@openbsd.org 2021-01-20T19:44:48Z urn:sha1:2e5c20414ff91e70d7dba4ec647a83703c5e31b2 2021-01-13T16:28:49Z cheloha cheloha@openbsd.org 2021-01-13T16:28:49Z urn:sha1:9589ba9d8c337eade22f8e39fd77554e71d63034 The global "tickadj" variable is a remnant of the old NTP adjustment code we used in the kernel before the current timecounter subsystem was imported from FreeBSD circa 2004 or 2005. Fifteen years hence it is completely vestigial and we can remove it. We probably should have removed it long ago but I guess it slipped through the cracks. FreeBSD removed it in 2002: https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d NetBSD and DragonflyBSD can probably remove it, too. We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2 and sysctl(8) accordingly. Hypothetically this change could break someone's sysctl(8) parsing script. I don't think that's very likely. ok mvs@ 2021-01-03T18:10:27Z rob rob@openbsd.org 2021-01-03T18:10:27Z urn:sha1:e992327fc31d0277a6f8518613a7db1b9face78b OK schwarze@, jmc@, deraadt@ 2020-12-29T12:28:23Z mglocker mglocker@openbsd.org 2020-12-29T12:28:23Z urn:sha1:cdf311310f1bca9abe45729faa364c27320bf917 With help/input from jmc@ and kn@. ok jmc@ 2020-11-14T10:16:15Z jmc jmc@openbsd.org 2020-11-14T10:16:15Z urn:sha1:7447bb90f625d7cb6f76e9f039c21a8128bcb1e0 or pseudo terminals (visa); ok mpi visa 2020-11-05T16:04:39Z jmc jmc@openbsd.org 2020-11-05T16:04:39Z urn:sha1:d50eda91847a59e3a1c927321b76844c4742de60 2020-10-25T00:54:51Z cheloha cheloha@openbsd.org 2020-10-25T00:54:51Z urn:sha1:018d9bc21737ff29df69832acedefe06041857b4 The clock_gettime.2 page is clumsy. It will be easier to use if it is reorganized to emphasize clock_gettime(2), a general and widely used interface, over clock_settime(2), a special-purpose and rarely used interface. While doing that I found a bunch of other things I wanted to tweak or improve: - Simplify the NAME summary. No need to mention "calibration" or "date". - "now", "res", and "clock" are better argument names than "tp" and "clock_id". - The CLOCK_* list is a bunch of fragments. Rewrite the list to make it easier to understand what the clocks represent and how they behave. - Mention clock_settime(2) *after* the list of clocks. Almost nobody needs to use it. It shouldn't lead the page alongside clock_gettime(2). - Drop the adjtime(2) reference. We could mention it in a CAVEATS section but it definitely doesn't belong here in the DESCRIPTION. - Drop the useless init(8) reference. - Add a bunch of EXAMPLES demonstrating how to actually use each clock. - Clean up the ERRORS. - Update the cross references. - Add a HISTORY for the interfaces and each clock. High-level structural ideas from jmc@ and schwarze@. Edited by jmc@. ok jmc@, probably ok schwarze@