The logrotate bug in samba-2.0.7-4 (as documented in bug #12832 and bug
#6998) caused samba log file to start multiply exponentially. This
exponential multiplication causes the number of files in /var/log/samba to
reach the filesystem maximal number of files limit. This means that it
becomes impossible for the system to create new files in /var partition
which creates problems with logging, mail delivery, etc. I know that the
logrotate problem is solved in Rawhide (and possibly - RedHat 7), but this
problem is very serious and warrants an Errata update for earlier versions
of RedHat. And you have to hurry - my guess is that in a few weeks
everybody who upgraded early will start hitting the #of files limit.
Sorry, I meant bug #9909 and bug #12832
slocate will fail to build it's database when the file names get too long. There is probably a bug in slocate too.
This should be fixed with the new errata release.
This is likely to happen again with new Samba as of samba-3.0.0-1beta3 (log
files specified as log.%m instead of %m.log in smb.conf).
Does this bug still apply to the latest beta?
# rpm -qa samba
log file = /var/log/samba/%m.log
max log size = 50
/bin/kill -HUP `cat /var/run/smbd.pid /var/run/nmbd.pid
/var/run/winbindd.pid 2> /dev/null` 2> /dev/null || true