cagney
cagney
> Usenet newsgroup comp.os.minix was very lively in 1987-1989 AST was clearly more than happy to accept contributions, such as bug fixes and ports to new architectures. This seems to...
> Honestly, I didn't get this impression while reading early posts in comp.os.minix. If your talking about 90s, it's possible. But still, there were various forks like Minix VMD or...
> Unfortunately I cannot reproduce the error, Part my fault. It turns out that the just released FreeBSD 14 hasn't updated their fping package (it's still 5.0) so it doesn't...
Off hand, would you know which clock: ``` /* ancilliary data */ { struct timespec reply_timestamp_ts; for (cmsg = CMSG_FIRSTHDR(&recv_msghdr); cmsg != NULL; cmsg = CMSG_NXTHDR(&recv_msghdr, cmsg)) { if (cmsg->cmsg_level...
I'm pretty sure it is CLOCK_REALTIME, which, on linux, leads to: ``` $ ./src/fping -z 0xffff 127.0.0.1 ./src/fping: count: 1, retry: 3, interval: 10 ms perhost_interval: 1000 ms, timeout: 500...
My thought, having worked through this, is to reject this patch and instead simplify the conditional code so it always uses CLOCK_REALTIME. The real cause of the FreeBSD problems is...
perhaps whack shutdown should send a signal
it would be much more robust the problem is whack expects to open a socket and have pluto close it when it finally exits
`WHACK_BASIC_MAGIC` indicates that either of the fields `.whack_shutdown` and `.whack_status` are valid. If either of those fields move, then WHACK_BASIC_MAGIC needs to be updated. The last update was in 2012...