GIT_LOG_ACTENT GIT_LOG_ACTEXIT GIT_LOG_ALL GIT_LOG_ALWAYS GIT_LOG_ALWAYS_S GIT_LOG_ARGS GIT_LOG_COMMS GIT_LOG_DEBUG GIT_LOG_ERRORS GIT_LOG_INST GIT_LOG_MSG GIT_LOG_STARTUP GIT_LOG_USER1 GIT_LOG_USER2 GIT_LOG_USER3 GIT_LOG_USER4 GIT_LOGGER_M_NO_FSYNC GitLoggerFile GitLoggerFlushAlways GitLoggerInit LOG_ACTENT LOG_ACTEXIT LOG_ALL LOG_ALWAYS LOG_ALWAYS_S LOG_ARGS LOG_COMMS LOG_DEBUG LOG_ERRORS LOG_INST LOG_MSG LOG_STARTUP LOG_USER1 LOG_USER2 LOG_USER3 LOG_USER4

GIT_LOGGER_M_NO_FSYNC #define GIT_LOGGER_M_NO_FSYNC   1 /* If set, don't fsync on flush */ C interface to tuning GitLogger. NewSetting is the new settings to apply. If OldSettings is non-zero, the previous settings are written here. This function allows us to tune GitLogger effiency vs other events. By default - GitLoggger will flush and fsync() the log file each time DitsMsgReceive() returns (LogFlush() events). We can turn this off by setting the GIT_LOGGER_M_LOG_FLUSH_OFF flag. Alternatively, we could do the STDIO flushing but turn the (rather expensive) fsync() call off using GIT_LOGGER_M_LOG_NO_FSYNC (This defaults to being set under Linux, where fsync() is expensive). We could also ensure that every message is flushed immediately by setting GIT_LOGGER_M_FLUSH_ALWAYS.