Many issues were reported with the current implementation of the RollingFileAppender so that a rewrite seems sensible.
Create a Replacement/Alternative to RollingFileAppender that works
RollingFileAppender crashes when missing logfile no 3+4
RollingFileAppender extension that backs up only a last specified period (days, hours, etc.) proposal
Failed to create netstandard version of logger
FileAppender.InterProcessLock.AcquireLock blocks everything
RollingFileAppender can't log to the same file from processes running under different accounts
Add new locking model to the FileAppender that works fine when multiple processes log and roll the same file
RollingFileAppenders that log to a network share from a web application fail to resume logging in the event the network share is disconnected/reconnected/failsover
RollingFileAppender generates unexpected filename and/or causes IIS to hang
Rolling files backups is not decreasing when updating MaxSizeRollBackups
RollingFileAppender with varying dynamic filenames not working
create a more directory when log files.
Rolling appender doesnt roll 0kb file, configured to roll on date.
multiple users overwrite existing log file when RollingFileAppender is rolling over date and minimal locking is used
GetLogger creates rolling files even for the unreferenced files
Log file will be override
Issue with rolling based on a date
RollingFileAppender stops logging intermittently when it tries to roll over the log file
RollingFileAppender: Cannot RollFile ... Source does not exist
RollingFileAppender does not delete file when RollingStyle = log4net.Appender.RollingFileAppender.RollingMode.Once
Rolling files on date/time boundaries doesn't support a maximum number of backup files.
RollingFileAppender file names do not support UTC
Allow to specify file name as wildcard pattern