i have searched for typical Samba log entries ( [200[0123]/.................\]' ) and found more logfile entries in different files:
File: /home/markus/CUECards/markus ELZET80.bak from 2003-05-07
[2003/05/07 15:07:52, 1] smbd/service.c:close_cnum(655)
cheops (192.168.17.45) closed connection to service markusFile: /samba/arev/VERKAUF/REV28819.OV from 2003-02-14
[2003/02/14 12:21:52, 1] smbd/service.c:make_connection(615)
chui (192.168.17.55) connect to service main as user walter (uid=500, gid=101) (pid 26489)
File: /samba/main/Produktion-Programmer/Produktion_beipackzettel.wpd ???
[2003/02/28 12:48:21, 1] smbd/service.c:close_cnum(655)
cheops (192.168.17.45) closed connection to service main
-> File can be open by Wordperfect ??!!!File: /samba/team/markus/mCAT-Freigaben/mcat-Freigabe_TSMCPU32H2CP_R108.wpd from 2003-02-10
[2003/02/10 10:29:45, 2] smbd/open.c:open_file(216)
markus opened file markus/mCAT-Freigaben/mcat-Freigabe_TSMCPU32H2CP_R108.wpd read=Yes write=Yes (numopen=2)
-> File can't be openend with Wordperfect
The Samba log under the filename appears inside the files.
You can see i have this problem at least from 2003-02-10. The Problem: At this time i used Samba 2.2.3a-12 (Debian stable) From 2003-04-07 i used Samba 2.2.8a
Jeremy Allison schrieb:
On Wed, Sep 10, 2003 at 06:17:43PM +0200, Markus Ungermann wrote:
Hello,
i have this problem again. I have samba logs, from log.smbd, inside my Wordperfect-Document:
[2003/09/09 16:42:33, 2] smbd/close.c:close_normal_file(229) markus closed file SftemBASIC/Testprogramme/2.9_Structure.b~RFf12cf7.TMP (numopen=4) [2003/09/09 16:42:33, 2] smbd/open.c:open_file(246) markus opened file SftemBASIC/test/m3/M3/workbench/EMBWorkBench.exe read=Yes write=No (numopen=5) [2003/09/09 16:42:33, 2] smbd/close.c:close_normal_file(229) markus closed file SftemBASIC/test/m3/M3/workbench/EMBWorkBench.exe (numopen=4) ä < ” ì D œ ô L ¤ / ÓÔ2 ÔÔ3 ÔÓ
The last 3 Lines are the Wordperfect lines. This is right, the samba logs before are wrong.
We've seen this on a couple of systems, SuSE and now Debian. We've never been able to reproduce it reliably. Our current best guess is it might be a glibc bug. What version of glibc do you have ?
Can you reproduce this ? If so, can you get an strace ?
Jeremy
-- Mit freundlichen Gruessen / Best regards
Markus Ungermann
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
