[Samba] Samba on Snap
Hi, We have a snap server 4400 which is running Samba and which we have successfully added to our Samba domain which is running on a Sun. However, when we save a file on the Snap server, the unix owner/group are set incorrectly to the values 20111 and 20002. A file saved on the Sun server has the correct unix owner/group. Consequently, the file save on the snap server cannot be edited at the unix level by the same user who created it on the PC! Does anyone know why this is and how we might correct it? We are not running winbindd on the Sun server, but we are on the Snap (the default). Could this be the cause? Thanks in advance for any answers. David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] RE: NFS mount problem
We have also discovered that Samba sessions are disconnecting even though the user is not accessing the NFS mounted directory. This is resulting in lots of dormant samba processes, and Outlook etc complaining that another machine has the file locked. When the NFS directory is removed, the dormant processes disappeared. David -Original Message- From: ALLEN, David Sent: 13 December 2004 10:47 To: '[EMAIL PROTECTED]' Subject: NFS mount problem Hi, We have a major problem using Samba to access NFS mounted directories. The directory in question is on a Snap server running OS 3, and Samba is running on a new Sun V250 running Solaris 9; the NFS directory is mounted using udp. The problems occur when trying to load a file, which causes the samba process to crash. Another process starts automatically, crashes and so forth. However, the exact same configuration, NFS mount, Samba version etc works fine on an old Sun Utlra 10, also running Solaris 9! Also, everything works fine at the Unix level on both machines. All oplocks options are set on in smb.conf, and a copys of the log file when I try to open the file are included below, with log level set at 2 and 3. Thanks in advance. David Log level 3: UNIX uid 15001 is UNIX user shpguest, and will be vuid 102 [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1372 of length 86 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBtconX (pid 28589) conn 0x0 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/service.c:make_connection_snum(472) Connect path is '/tmp' for service [IPC$] [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(251) [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(252) se_access_check: user sid is S-1-5-21-1460809338-1000444070-3279871270-501 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-514 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-32-546 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-5427 [2004/12/13 10:33:55, 3] smbd/vfs.c:vfs_init_default(203) Initialising default vfs hooks [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(251) [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(252) se_access_check: user sid is S-1-5-21-1460809338-1000444070-3279871270-501 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-514 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-32-546 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-5427 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (15001, 2213) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/service.c:make_connection_snum(648) duk652-008167 (6.52.14.33) connect to service IPC$ initially as user shpguest (uid=15001, gid=2213) (pid 28589) [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/reply.c:reply_tcon_and_X(456) tconX service=IPC$ [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1373 of length 90 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (305, 2200) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(.) returning 0664 [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(105) error string = Is a directory [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(129) error packet at smbd/nttrans.c(867) cmd=162 (SMBntcreateX) NT_STATUS_FILE_IS_A _DIRECTORY [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1374 of length 152 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(do/publications/temp/Thumbs.db) returning 0664 [2004/12/13 10:33:55, 3] smbd/open.c:open_file(178) Error opening file do/publications/temp/Thumbs.db (No such file or directory) (local_flags=0) (flags=0) [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(105) error string = No such file or directory [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(129) error packet at smbd/trans2.c(2240) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NA ME_NOT_FOUND [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1375 of length 152 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(do/publications/temp/Thumbs.db) returning 0664 [2004/12/13 10:33:55, 3
[Samba] NFS mount problem
Hi, We have a major problem using Samba to access NFS mounted directories. The directory in question is on a Snap server running OS 3, and Samba is running on a new Sun V250 running Solaris 9; the NFS directory is mounted using udp. The problems occur when trying to load a file, which causes the samba process to crash. Another process starts automatically, crashes and so forth. However, the exact same configuration, NFS mount, Samba version etc works fine on an old Sun Utlra 10, also running Solaris 9! Also, everything works fine at the Unix level on both machines. All oplocks options are set on in smb.conf, and a copys of the log file when I try to open the file are included below, with log level set at 2 and 3. Thanks in advance. David Log level 3: UNIX uid 15001 is UNIX user shpguest, and will be vuid 102 [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1372 of length 86 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBtconX (pid 28589) conn 0x0 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/service.c:make_connection_snum(472) Connect path is '/tmp' for service [IPC$] [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(251) [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(252) se_access_check: user sid is S-1-5-21-1460809338-1000444070-3279871270-501 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-514 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-32-546 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-5427 [2004/12/13 10:33:55, 3] smbd/vfs.c:vfs_init_default(203) Initialising default vfs hooks [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(251) [2004/12/13 10:33:55, 3] lib/util_seaccess.c:se_access_check(252) se_access_check: user sid is S-1-5-21-1460809338-1000444070-3279871270-501 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-514 se_access_check: also S-1-1-0 se_access_check: also S-1-5-2 se_access_check: also S-1-5-32-546 se_access_check: also S-1-5-21-1460809338-1000444070-3279871270-5427 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (15001, 2213) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/service.c:make_connection_snum(648) duk652-008167 (6.52.14.33) connect to service IPC$ initially as user shpguest (uid=15001, gid=2213) (pid 28589) [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/reply.c:reply_tcon_and_X(456) tconX service=IPC$ [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1373 of length 90 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (305, 2200) - sec_ctx_stack_ndx = 0 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(.) returning 0664 [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(105) error string = Is a directory [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(129) error packet at smbd/nttrans.c(867) cmd=162 (SMBntcreateX) NT_STATUS_FILE_IS_A _DIRECTORY [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1374 of length 152 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(do/publications/temp/Thumbs.db) returning 0664 [2004/12/13 10:33:55, 3] smbd/open.c:open_file(178) Error opening file do/publications/temp/Thumbs.db (No such file or directory) (local_flags=0) (flags=0) [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(105) error string = No such file or directory [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(129) error packet at smbd/trans2.c(2240) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NA ME_NOT_FOUND [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1375 of length 152 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid 28589) conn 0x2d7ee8 [2004/12/13 10:33:55, 3] smbd/dosmode.c:unix_mode(111) unix_mode(do/publications/temp/Thumbs.db) returning 0664 [2004/12/13 10:33:55, 3] smbd/open.c:open_file(178) Error opening file do/publications/temp/Thumbs.db (No such file or directory) (local_flags=0) (flags=0) [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(105) error string = No such file or directory [2004/12/13 10:33:55, 3] smbd/error.c:error_packet(129) error packet at smbd/trans2.c(2240) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NA ME_NOT_FOUND [2004/12/13 10:33:55, 3] smbd/process.c:process_smb(1092) Transaction 1376 of length 158 [2004/12/13 10:33:55, 3] smbd/process.c:switch_message(887) switch message SMBntcreateX (pid
[Samba] RE: NFS mounted directory
Hi, We may have solved this problem by switching the NFS mount from tcp to udp (specify proto=udp in vfstab). Has anyone any suggestions why this should solve the problem, and are there any disadvantages? Thanks in advance. David -Original Message- From: ALLEN, David Sent: 03 December 2004 17:47 To: '[EMAIL PROTECTED]' Subject: NFS mounted directory Hi, Has anyone any ideas what is causing my smbd processes to crash? The files being accessed via samba are on an NFS mounted directory. In the samba log file I am getting the following errors: [2004/12/03 16:31:33, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 2181 9 on port 53336 for dev = 2c2, inode = 297939333 for dev = 2c2, inode = 297939333, tv_sec = 41b09217, tv_usec = 2be1b [2004/12/03 16:31:33, 0] smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock left by process 21819 after break ! For file 5000_photos/Thumbs.db, dev = 2c2, inode = 297939333. Deleting it to continue ... [2004/12/03 16:31:33, 0] lib/util.c:smb_panic(1055) PANIC: open_mode_check: Existant process 21819 left active oplock. and a truss -d for the process which has crashed gives the following: *** SUID: ruid/euid/suid = 0 / 2053 / 2053 *** *** SGID: rgid/egid/sgid = 0 / 500 / 500 *** poll(0xFFBEED08, 2, 32000) (sleeping...) poll(0xFFBEED08, 2, 32000) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, s m b d / o p l o c k ..., 13) = 13 write(25, :, 1) = 1 write(25, r e q u e s t _ o p l o.., 20) = 20 write(25, (, 1) = 1 write(25, 1 0 2 6, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, r e q u e s t _ o p.., 133)= 133 getuid()= 0 [2053] write(25, f o r d e v = .., 75) = 75 fcntl(14, F_SETLKW64, 0xFFBEEEA8) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, s m b d / o p e n . c, 11) = 11 write(25, :, 1) = 1 write(25, o p e n _ m o d e _ c h.., 15) = 15 write(25, ( 5 5 5, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, o p e n _ m o d e _.., 164)= 164 kill(21819, SIG#0) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, l i b / u t i l . c, 10) = 10 write(25, :, 1) = 1 write(25, s m b _ p a n i c, 9) = 9 write(25, (, 1) = 1 write(25, 1 0 5 5, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, P A N I C : o p e.., 69) = 69 getuid()= 0 [2053] write(25, \n, 3) = 3 getuid()= 0 [2053] sigaction(SIGABRT, 0x, 0xFFBEEFB0) = 0 llseek(0, 0, SEEK_CUR) = 0 sigaction(SIGABRT, 0xFFBEEE80, 0xFFBEEF00) = 0 sigprocmask(SIG_UNBLOCK, 0xFFBEEF30, 0x) = 0 getpid()= 22241 [21295] kill(22241, SIGABRT)= 0 Received signal #6, SIGABRT [default] siginfo: SIGABRT pid=22241 uid=0 *** process killed *** In samba I have all op locks options turned on. Is the NFS directory( on a snap server) not responding correctly to the op locks, or is there another problem? Thanks in advance. David -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] NFS mounted directory
Hi, Has anyone any ideas what is causing my smbd processes to crash? The files being accessed via samba are on an NFS mounted directory. In the samba log file I am getting the following errors: [2004/12/03 16:31:33, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 2181 9 on port 53336 for dev = 2c2, inode = 297939333 for dev = 2c2, inode = 297939333, tv_sec = 41b09217, tv_usec = 2be1b [2004/12/03 16:31:33, 0] smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock left by process 21819 after break ! For file 5000_photos/Thumbs.db, dev = 2c2, inode = 297939333. Deleting it to continue ... [2004/12/03 16:31:33, 0] lib/util.c:smb_panic(1055) PANIC: open_mode_check: Existant process 21819 left active oplock. and a truss -d for the process which has crashed gives the following: *** SUID: ruid/euid/suid = 0 / 2053 / 2053 *** *** SGID: rgid/egid/sgid = 0 / 500 / 500 *** poll(0xFFBEED08, 2, 32000) (sleeping...) poll(0xFFBEED08, 2, 32000) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, s m b d / o p l o c k ..., 13) = 13 write(25, :, 1) = 1 write(25, r e q u e s t _ o p l o.., 20) = 20 write(25, (, 1) = 1 write(25, 1 0 2 6, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, r e q u e s t _ o p.., 133)= 133 getuid()= 0 [2053] write(25, f o r d e v = .., 75) = 75 fcntl(14, F_SETLKW64, 0xFFBEEEA8) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, s m b d / o p e n . c, 11) = 11 write(25, :, 1) = 1 write(25, o p e n _ m o d e _ c h.., 15) = 15 write(25, ( 5 5 5, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, o p e n _ m o d e _.., 164)= 164 kill(21819, SIG#0) = 0 time() = 1102092631 getuid()= 0 [2053] write(25, [, 1) = 1 write(25, 2 0 0 4 / 1 2 / 0 3 1.., 19) = 19 write(25, , 0, 3) = 3 write(25, ] , 2)= 2 write(25, l i b / u t i l . c, 10) = 10 write(25, :, 1) = 1 write(25, s m b _ p a n i c, 9) = 9 write(25, (, 1) = 1 write(25, 1 0 5 5, 4)= 4 write(25, )\n, 2)= 2 getuid()= 0 [2053] write(25, P A N I C : o p e.., 69) = 69 getuid()= 0 [2053] write(25, \n, 3) = 3 getuid()= 0 [2053] sigaction(SIGABRT, 0x, 0xFFBEEFB0) = 0 llseek(0, 0, SEEK_CUR) = 0 sigaction(SIGABRT, 0xFFBEEE80, 0xFFBEEF00) = 0 sigprocmask(SIG_UNBLOCK, 0xFFBEEF30, 0x) = 0 getpid()= 22241 [21295] kill(22241, SIGABRT)= 0 Received signal #6, SIGABRT [default] siginfo: SIGABRT pid=22241 uid=0 *** process killed *** In samba I have all op locks options turned on. Is the NFS directory( on a snap server) not responding correctly to the op locks, or is there another problem? Thanks in advance. David -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba, CUPS and Windows Printer Queue
Hi, I cannot help you, but we have experienced a similar problem with 3.0.2a running on Solaris and cups. Old print jobs remain in the queue, connection to the printers is lost, and worse, samba crashes for the user, causing Outlook to lock up. As a quick fix we have deleted the printing lock files in /usr/local/samba/var/locks. Samba.org have said it may be bug 1147, and recommend upgrading to 3.0.5. If you find anything else I would be interested. David -Original Message- From: Collins, Kevin [mailto:[EMAIL PROTECTED] Sent: 26 July 2004 12:51 To: [EMAIL PROTECTED] Subject: [Samba] Samba, CUPS and Windows Printer Queue I've had a Samba 3.0.2 Print Server running for nearly 7 months now without too much of a hitch on RedHat Enterprise ES 3.0. Late last week, RedHat issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base. So when I did the up2date this weekend as part of my normal maintenance, this server was updated and everything appeared to be fine. Things are working, print jobs are getting sent so for the most part I am happy. But, I am experiencing one problem. The Windows printer queue (I have a mixed set of clients - mostly Windows 2000 and some Windows XP) show active jobs even *after* the job has completed. I've checked the CUPS Web-Management console and there are no active jobs. Yet on my Windows machine, I have 4 printers that show to have a total of 47 print jobs in the queue. Here is a snippet of the Print Server's smb.conf: = [global] # Server Name and description workgroup = nesbitt.local netbios name = valykyrie server string = Samba 3 Print and Backup Server # Samba log information log file = /var/log/samba/%m.log max log size = 7168 # Security information security = user encrypt passwords = yes # To help performance socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 # Settings for PDC setup local master = no os level = 0 domain master = no preferred master = no domain logons = no # Activate these Network Services wins server = 10.200.8.253 # LDAP Declarations -- Needed to allow the LDAP backend to work ldap suffix = dc=nesbitt,dc=local ldap admin dn = cn=Manager,dc=nesbitt,dc=local passdb backend = ldapsam:ldap://stargazer.nesbitt.local ldap delete dn = no ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap filter = ((uid=%u)(objectClass=sambaSamAccount)) ldap passwd sync = yes # Global settings for printers printing = cups printcap name = cups load printers = yes use client driver = yes # Oplocks settings - disable all oplocks for compatibility reasons oplocks = no level2 oplocks = no kernel oplocks = no [printers] comment = All Printers path = /var/spool/samba public = yes guest ok = yes writeable = no printable = yes = Has anyone experienced this? What other information is needed to help diagnose this issue? Any help would be welcomed... -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba lock problem?
Hi, Is there a locking problem with version 3.0.2a? We have been running this version over the past several weeks with no problems, but over the past few days have been experiencing horrendous apparently random problems with Outlook, Printing and Excel. Outlook fails with the error folder being modified by another workstation Excel gives disk full errors Printing stops working. The reason I think it may be a locking problem is because printing started working when the .tdb files were removed from /usr/local/samba/var/locks/printing. I am also getting errors like the following in the log file which may or may not be relevant [2004/07/22 10:59:07, 0] lib/fault.c:fault_report(36) === [2004/07/22 10:59:07, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 6 in pid 19546 (3.0.2a) Please read the appendix Bugs of the Samba HOWTO collection [2004/07/22 10:59:07, 0] lib/fault.c:fault_report(39) === [2004/07/22 10:59:07, 0] lib/util.c:smb_panic(1400) Samba is running on Solaris v9 4/04. Thanks in advance for any help David -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Re: Samba lock problem?
Thanks for your reply. When we first noticed the problem, oplocks and oplocks2 were on. Subsequently, we have turned them off for outlook .pst files using /*.pst/ in the veto oplock files option. This looks to have stopped oplocks for pst files, as shown in smbstatus -u but unfortunately has not fixed the problem! Any other suggestions would be appreciated! David -Original Message- From: Michael Lueck [mailto:[EMAIL PROTECTED] Sent: 23 July 2004 13:19 To: [EMAIL PROTECTED] Subject: [Samba] Re: Samba lock problem? ALLEN, David (Shipley) wrote: Is there a locking problem with version 3.0.2a? Just as a thought, have you disabled oplocks and oplocks2? Though I would more expect corrupted files if this were the case than Samba feeling pain and putting it in its log, it might be worth a try. -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba