You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On an unbusy server, I notice ordinary file logging (not stderr, or stdout) doesn't happen until a new log entry is placed. looking at /src/logging.c I see fflush(), but only if 1 second has elapsed. Unfortunately this check only happens upon the next log entry, so the previous log entry get trapped in the kernel.
The text was updated successfully, but these errors were encountered:
On an unbusy server, I notice ordinary file logging (not stderr, or stdout) doesn't happen until a new log entry is placed. looking at /src/logging.c I see fflush(), but only if 1 second has elapsed. Unfortunately this check only happens upon the next log entry, so the previous log entry get trapped in the kernel.
The text was updated successfully, but these errors were encountered: