Ticket #36 (assigned defect)
max log file does not work (i.e logfile grows forever)
| Reported by: | guest | Owned by: | diver |
|---|---|---|---|
| Priority: | critical | Milestone: | Samba Server for eCS (OS/2) 1.1.x |
| Component: | Samba Server | Version: | Server 3.3.x |
| Keywords: | log file size | Cc: | herwig.bauernfeind@… |
Change History
comment:2 Changed 6 years ago by guest
Okay, to reproduce the problem, add
max log size = 1000
to the [global] section of smb.conf. Now the logfile should not grow bigger than 1000 kb i.e 1 MB.
Setting the loglevel to 5 (or higher) and running a dir /s /-p from a client against a share full of files should produce a "bigger" logfile within some 30 seconds or so.
comment:3 Changed 5 years ago by herwigb
- Priority changed from major to blocker
This is becoming a a major annoyance...
comment:6 Changed 4 years ago by diver
- Milestone changed from Samba Server for eCS (OS/2) 1.0.1 to Samba Server for eCS (OS/2) 1.1.0 alpha
permanant restriction for 1.0.1 (samba code 3.0). we try to find a solution for 1.1.0 (samba code 3.3)
comment:8 Changed 23 months ago by herwigb
- Priority changed from major to critical
- Version changed from 3.0.26a to 3.3.x
comment:9 Changed 23 months ago by herwigb
- Owner changed from psmedley to diver
- Status changed from new to assigned
comment:10 Changed 23 months ago by herwigb
It looks like this is becoming more an more important again - Samba 3.3.x prodcues more logfiles. I noticed that with loglevel 3 Samba 3.3.15 produced 3GB+ logfiles in 3 days. Especially log.smbd..UNKNOWN is more than 2GB in size and cannot be deleted while smbd is running.
I think the bug is located in \source\lib\debug.c, function check_log_size(), line 708 to 715.