Samba logging behavior on new files
Gerald (Jerry) Carter
jerry at samba.org
Mon Apr 2 20:39:45 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
> Hi list,
> I have home made program, which uses File Alteration Monitor library
> to watch samba log files for new file creation in samba share
> This technique works fine when I use GNU/Linux machine as client and
> it fails when I use Windows machine as client. The cause of failure
> is, samba server creates different pattern of logs and sometimes it
> does not create log entries on new file creation.
> New file creation is done by copying file to share directory after
> mounting it.
> Log configuration of samba server is
> log file = /var/log/samba/%U.log
> log level = 2
I don't understand what your problem is.
> Below is log entries when GNU/Linux is used.
> [2007/03/20 18:01:18, 2] smbd/open.c:open_file(245)
> b2bc1ir opened file outbox/echoserver read=Yes write=Yes (numopen=1)
> [2007/03/20 18:01:18, 2] smbd/reply.c:reply_mknew(1324)
> new file outbox/echoserver
> [2007/03/20 18:01:18, 2] smbd/close.c:close_normal_file(270)
> b2bc1ir closed file outbox/echoserver (numopen=0)
> Below is log entries when Windows is used.
Linux clients and Windows clients do different operations
to achieve the same result. What are you expecting?
Samba ------- http://www.samba.org
Centeris ----------- http://www.centeris.com
"What man is a man who does not make the world better?" --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the samba-technical