Andrew Daugherity

No, those are separate issues. Handling xz archives is great, but is unrelated to scheduling, aside from now processing archive files which may have been previously skipped. If logrotate and logwatch are both scheduled via systemd timers (which is the direction many distros seem to be moving in), then without this patch they will be started in parallel, and there is indeed a race condition -- e.g. logrotate could move/change a file while logwatch is processing it. (This could also happen if one is...

man page patch

systemd fixes/improvements -- run before logrotate

extra blank lines in httpd "Attempts to use known hacks" output

I think #436 was closed prematurely, as it still segfaults after entering a password on macOS, even though std=gnu99 is now used. I tracked that down to the getpass() prototype not being defined -- turns out on macOS X's <unistd.h>, getpass() is defined (or not) based on the value of _POSIX_C_SOURCE, which is in turn set based on _XOPEN_SOURCE. _BSD_SOURCE does not matter here, unlike e.g FreeBSD & OpenBSD which use something like #if (defined _BSD_SOURCE) || (_XOPEN_SOURCE <= 500). Compiler warning...

After further testing and reading of the code, I determined that it intends to run...

infinite loop & memory leak in cron.php