------------------------------------------------------------------------- WARNING: I filed this under version 3.0.30 as bugzilla is not configured for version 3.0.31, but this goes against version 3.0.31! ------------------------------------------------------------------------- I have configured Samba 3.0.31 to log into one specific file. What I get is that each process logs into its own file, which is extremely annoying. Could this please be turned back to the logging like in 3.0.2x versions??!!!! It was annoying enough that each process began its own log file, but I could handle this by removing the file with a timeout after starting SAMBA, but with 3.0.31, the logging into the separate files does not stop anymore. From the configuration: # cat /etc/cfg_user/smb.conf.ads | grep log winbind offline logon=True log file=/var/log/adsamba/smblog.ad log level=6 max log size=0 # ls /var/log/adsamba/ cores log.wb-DOMAIN smblog.ad log.nmbd log.winbindd log.smbd log.winbindd-idmap
Nothing has changed in this code that I am aware of. Which previous version are you comparing the behavior against?
(In reply to comment #1) > Nothing has changed in this code that I am aware of. Which previous version > are you comparing the behavior against? > 3.0.23 I noticed now, that 3.0.30 has the same bug. The older versions changed from their individual log-files to the configured logfile once they had interpreted the configuration. It is extremely important to have only one log file (of very limited size) for devices with very few memory resources. Otherwise, the log-file directory cannot be put into memory but has to be put onto the harddisk. This means, that the hard disk never sleeps, so logging has to be turned off completely. And that is not really nice.
the "loggin" parameter probably helps you do what you want.