O_NOFOLLOW acts only on *the last component*, so on open("/foo/bar/baz") only when baz is a symlink open fails. Checking every path component is not viable. gh issue #5 related (sort of)

Since there was 0 reports in a month can I assume it's not actually used anywhere?

used by glibc on aarch64. Found and tested by pine, thanks!

Just read in a mail from Ingo to tech@ > Using \\ outside macro definitions (i.e., outside the bodies of roff(7) > .de and similar requests) is almost always wrong even in low-level roff > code, and \\ must never be used in manual pages.

An un-initialized field in the configless code path leads to a crash on the first request.

Error and warning messages are prefixed with "error: " and "warning: " correspondingly to ease integration with automated tooling. `yywarn' function added. Off-by-one line numbers in warnings are fixed. Two error messages are reworded to avoid repeating like "error: error in server directive" or "error: syntax error".