Bug 5625 - Samba 3.0.31 logs to wrong file
Samba 3.0.31 logs to wrong file
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.31
Other Windows 2000
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-18 09:14 UTC by Jens Nissen
Modified: 2008-07-22 04:46 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Nissen 2008-07-18 09:14:43 UTC
-------------------------------------------------------------------------
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
Comment 1 Gerald (Jerry) Carter 2008-07-21 07:36:56 UTC
Nothing has changed in this code that I am aware of.  Which previous version are you comparing the behavior against?
Comment 2 Jens Nissen 2008-07-22 04:46:52 UTC
(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.