Lack of nonblocking sockets can have bad effects when they are needed. Currently fc_nonblock() uses just log_debug() to inform user about this when it happens. Turn that log to log_warn() in S3_1 and master (where warn level exist). S3_0 should probably go to log_normal() (and not all the way to log_error())?
Lack of nonblocking sockets can have bad effects when they are needed. Currently fc_nonblock() uses just log_debug() to inform user about this when it happens. Turn that log to log_warn() in S3_1 and master (where warn level exist). S3_0 should probably go to log_normal() (and not all the way to log_error())?