Custom Query (292 matches)

Currently, smb.cmd creates ZIPs for log files (/MPTN/etc/samba/log) and for configuration files (from both /etc and /MPTN/etc). There doesn't seem to be any limit on the total size of the backup files. As a result, it can grow too big after some time of extensive usage. Here it grew up to more than 100MB in total (note that log level is 0).

The log file backups seem to grow too fast when samba crashes and spits out a lot of stuff in the log files. Also, the files in the lock directory are sometimes very big and this may create configuration backups enormously big.

I think there should be a limit on the overall size of the backup files as well as on their age. A month and 50 MB seems like a sane default for me. When reaching any of these limits, the oldest log files should be deleted.

I ran yum update on my server today and after rebooting everything worked except Samba server 3.5.19 would not start. It has been working fine for a long time. I get this message:

[C:\programs\samba]smb start

512 +++ GLOBAL.idmap_config_ * _!_backend = 'tdb';

REX0041: Error 41 running C:\programs\samba\smb.cmd, line 512: Bad arithmetic conversion

512 +++ Interpret istr; 302 +++ Call LoadSmbConf?; 29 +++ Call _SambaGetProperties;

Any idea what this may indicate? I tried copying original gccxxx.dll files to the Samba directory, but it did not help. SMBD.exe will also not run - it exits silently. I'll have to back out the yum updates....

I have Samba with EVFSGUI v. 2,5 RC 7 on my eCS 2.1 system. When I start Samba in order to connect to my NAS box (Zyxel NSA 220 plus), I quickly get an error message as shown in the attached screen dump. Clicking "OK" on the error message shuts down the Samba window. What is wrong here?