search for: set_share_mode

Samba 1.9.17p1. The log file contains Ks of messages like this: ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /usr/a...

Last friday we upgraded from 1.9.17p4 to version 1.9.18p3 on a HP-UX 9.04 machine. Now we get lots of entries in the log.smb file like: ERROR: del_share_mode: failed to ftruncate share mode file /programs/samba/var/locks/share.1073807365.8199 to size 42 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /programs/samba/var/locks/share.1073807365.8195 to size 42 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /programs/samba/var/locks/share.1073807365.8200 to size 42 (Permission denied) ERROR: set_share_mode: failed to ftruncate sh...

.../05/28 08:56:33, 3] lib/util.c:unix_clean_name(609) unix_clean_name [home/eft_oper/eftcomc3/user1.ntx] [1999/05/28 08:56:33, 2] smbd/open.c:open_file(577) arcservebackup opened file home/eft_oper/eftcomc3/user1.ntx read=Yes write=No (numopen=3) [1999/05/28 08:56:33, 3] locking/locking_shm.c:shm_set_share_mode(456) set_share_mode: Created share record for home/eft_oper/eftcomc3/user1.ntx (dev 808 inode 1574995) [1999/05/28 08:56:33, 3] locking/locking_shm.c:shm_set_share_mode(495) set_share_mode: Created share entry for home/eft_oper/eftcomc3/user1.ntx with mode 0x40 pid=32737 [1999/05/28 08:56:33, 3...

...clean_name [dvise-dev/win32.d/src/dmcad/libdnrb/vc50.pch] calling open_file with flags=0x1 flags2=0x200 mode=0664 Allocated new file_fd_struct 4, dev = ffffffff, inode = ffffffff 04/16/1998 13:58:53 dvise opened file dvise-dev/win32.d/src/dmcad/libdnrb/vc50.pch read=No write=Yes (numopen=2 fnum=14) set_share_mode: Created share record for dvise-dev/win32.d/src/dmcad/libdnrb/vc50.pch (dev 2098183 inode 154502) set_share_mode: Created share entry for dvise-dev/win32.d/src/dmcad/libdnrb/vc50.pch with mode 0x11 pid=1726 04/16/1998 13:58:53 Transaction 218244 of length 52 switch message SMBwrite (pid 1726) Skipp...

...ir cache hit on . PRIVATE -> Private unix_clean_name [Private/Goyal_Sep98.PRZ] calling open_file with flags=0x2 flags2=0x0 mode=0664 Allocated new file_fd_struct 0, dev = ffffffff, inode = ffffffff 1998/10/08 13:50:32 axs opened file Private/Goyal_Sep98.PRZ read=Yes write=Yes (numopen=1 fnum=26) set_share_mode: Created share record for Private/Goyal_Sep98.PRZ (dev 1 inode 33106898) set_share_mode: Created share entry for Private/Goyal_Sep98.PRZ with mode 0x22 pid=33994 1998/10/08 13:50:32 Transaction 18 of length 94 switch message SMBopenX (pid 33994) Skipping become_user - already user unix_clean_name [...

...#39;s excellent book indicates it is a hacker option. As far as I can see there is no other documentation on this option. However I have a server (used for software distribution) to 100+ NT clients and it clearly ran out of shared memory eg: Jan 7 14:55:37 cedar.brunel.ac.uk smbd[27486]: ERROR:set_share_mode shmops-> shm _alloc fail! Jan 7 14:55:37 cedar.brunel.ac.uk smbd[27486]: ERROR shm_alloc : alloc of 56 by tes failed Jan 7 14:55:37 cedar.brunel.ac.uk smbd[27486]: ERROR:set_share_mode shmops-> shm _alloc fail! Jan 7 14:55:41 cedar.brunel.ac.uk smbd[28154]: PANIC ERROR:del_share_mode has...

...' listings with loglevel=4, maybe the experts can tell something from it: switch message SMBopenX (pid 142426) unix_clean_name [] unix_clean_name [] Allocated new file_fd_struct 3, dev = ffffffff, inode = ffffffff 1998/09/15 14:18:11 gg opened file ./ read=Yes write=No (numopen=3 fnum=91) set_share_mode: Created share record for ./ (dev 1 inode 25821394) set_share_mode: Created share entry for ./ with mode 0x40 pid=142426 del_share_modes Deleting share mode entry dev=1 ino=25821394 del_share_modes num entries = 0, deleting share_mode dev=1 ino=25821394 fd_attempt_close on file_fd_struct 3, fd...

...ean_name [/FABERLAB/suse.iso] [2000/06/02 15:17:32, 3] lib/util.c:unix_clean_name(522) unix_clean_name [FABERLAB/suse.iso] [2000/06/02 15:17:32, 2] smbd/open.c:open_file(599) maurice opened file FABERLAB/suse.iso read=No write=Yes (numopen=1) [2000/06/02 15:17:32, 3] locking/locking_shm.c:shm_set_share_mode(455) set_share_mode: Created share record for FABERLAB/suse.iso (dev 690 inode 44818) [2000/06/02 15:17:32, 3] locking/locking_shm.c:shm_set_share_mode(494) set_share_mode: Created share entry for FABERLAB/suse.iso with mode 0x11 pid=787 [2000/06/02 15:17:32, 3] smbd/process.c:process_smb(6...

...pid 909) chdir to / chdir to /usr/local/www/sites/wwwlocal2.nibsc.ac.uk/dbs/phonebook unix_clean_name [./README.TXT] unix_clean_name [README.TXT] Allocated new file_fd_struct 0, dev = ffffffff, inode = ffffffff 1998/10/21 14:00:19 dmccann opened file README.TXT read=Yes write=No (numopen=1 fnum=47) set_share_mode: Created share record for README.TXT (dev 786433 inode 106029) set_share_mode: Created share entry for README.TXT with mode 0x0 pid=909 1998/10/21 14:00:19 Transaction 18 of length 55 switch message SMBreadbraw (pid 909) chdir to / chdir to /usr/local/www/sites/wwwlocal2.nibsc.ac.uk/dbs/phonebook...

Thank you for the information that you have passed on to me. My own research has found that ftruncate is quite happy to set a file to the same size that it is already, so something else must be causing the problem. The comment before the ftruncate in set_share_mode says the file is being truncated just for safety, so normally it is probably not necessary to truncate the file. Regards, Tim > Tim Boorman > UNIX Systems Support > Lusis Limited, Technology Drive, Bridgend Science Park, Bridgend, > United Kingdom CF31 3UJ > Extension: 44966 >...

...flags = 01002 mode = 0760, fd = 24. [2003/02/11 10:19:47, 2] smbd/open.c:open_file(245) CSHENTO8 opened file STS107/DEBUG10 read=Yes write=Yes (numopen=1) [2003/02/11 10:19:47, 10] smbd/open.c:open_file_shared1(1042) open_file_shared : share_mode = 42 [2003/02/11 10:19:47, 10] locking/locking.c:set_share_mode(692) set_share_mode: creating entry for file STS107/DEBUG10. num_share_modes = 1 [2003/02/11 10:19:47, 10] locking/locking.c:print_share_mode_table(445) print_share_mode_table: share_mode_entry[0]: pid = 6357, share_mode = 0x42, desired_access = 0x3, port = 0x0, type= 0x0, file_id = 1, dev = 0x...

Prior to upgrading from RH7.0 to RH7.3 our Samba filserver worked perfectly. Now we are having locking problems. Initially Iused the same samba binaries built on RH70, I tried rebuilding Samba and reinstalling but it had no effect. If user bon opens an M$-Office file they frequently get a 'file is already in use by bob'. Sure enough smbstatus -L shows the file locked by bob, but bob

Although the bug in Samba 1.9.17p1 which caused "ERROR: set_share_mode: failed to ftruncate share mode file" messages in log.smb has been fixed in 1.9.17p2, empty share* files are not being deleted from the lock file directory. Regards, Tim > Tim Boorman > UNIX Systems Support > Lusis Limited, Technology Drive, Bridgend Science Park, Bridgend, > Un...

I'm looking at migrating a small Netware 3.12 server to a Linux box with samba for a small office. They use a DOS program called `ACCPAC' to do their accounting; both the program and it's data reside on different exported volumes on the netware system. I set up a linux box (for testing- deployment later, maybe) to make sure the program would run with samba before going ahead and just

...13:53:22, 0] lib/util.c:smb_panic2(1512) BACKTRACE: 16 stack frames: #0 smbd(smb_panic2+0x8a) [0xe44260] #1 smbd(smb_panic+0x19) [0xe4448c] #2 smbd [0xe30bff] #3 /lib/tls/libc.so.6 [0x6858e8] #4 smbd [0xe57d0d] #5 smbd [0xe582fe] #6 smbd(tdb_store+0x137) [0xe59426] #7 smbd(set_share_mode+0x1d3) [0xe00f09] #8 smbd(open_file_shared1+0xde2) [0xd1be6d] #9 smbd(reply_ntcreate_and_X+0x88f) [0xceefa8] #10 smbd [0xd2d4c2] #11 smbd(process_smb+0x19b) [0xd2d8fc] #12 smbd(smbd_process+0x15f) [0xd2e624] #13 smbd(main+0x875) [0xec0b37] #14 /lib/tls/libc.so.6(__libc_start_ma...

...and or that there are too many files open. The problem is not reproducable, but only happens from time to time (say every few hours). I've had a look at the samba logs for his pc and this is what happens at the time that he has the error. [1999/01/27 16:32:07, 0] locking/locking_shm.c:shm_set_share_mode(486) PANIC ERROR:set_share_mode num_share_mode_entries=-12 [1999/01/27 16:32:07, 2] locking/locking_shm.c:shm_del_share_mode(354) del_share_modes Deleting share mode entry dev=800047 ino=464779 [1999/01/27 16:32:07, 0] locking/locking_shm.c:shm_del_share_mode(367) PANIC ERROR:del_share_mod...

...0000B0, flags = 0101 mode = 0744, fd = 23. [2003/11/20 22:57:34, 2] smbd/open.c:open_file(245) nickgale opened file 800000B0 read=No write=Yes (numopen=1) [2003/11/20 22:57:34, 10] smbd/open.c:open_file_shared1(1042) open_file_shared : share_mode = 11 [2003/11/20 22:57:34, 10] locking/locking.c:set_share_mode(692) set_share_mode: creating entry for file 800000B0. num_share_modes = 1 [2003/11/20 22:57:34, 10] locking/locking.c:print_share_mode_table(445) print_share_mode_table: share_mode_entry[0]: pid = 18423, share_mode = 0x11, desired_access = 0x120196, port = 0x0, type= 0x0, file_id = 68, dev = 0...

...flags=0x0 flags2=0x0 mode=00 [2004/01/09 10:05:49, 2] smbd/open.c:open_file(250) PLAY opened file VIDEO/2003-1/DVm04-01.avi read=Yes write=No (numopen=1) [2004/01/09 10:05:49, 10] smbd/open.c:open_file_shared1(1126) open_file_shared : share_mode = 10 [2004/01/09 10:05:49, 10] locking/locking.c:set_share_mode(654) set_share_mode: creating entry for file VIDEO/2003-1/DVm04-01.avi. num_share_modes = 1 [2004/01/09 10:05:49, 10] locking/locking.c:print_share_mode_table(406) print_share_mode_table: share_mode_entry[0]: pid = 32295, share_mode = 0x10, desired_access = 0x10000, port = 0x0, type= 0x0, file_...

...h] [2005/04/22 12:21:36.364473, 2, pid=19888, effective(4294967294, 4294967294), real(0, 0)] smbd/open.c:open_file(602) iusr_hopper opened file test.sh read=No write=Yes (numopen=1) [2005/04/22 12:21:36.364579, 3, pid=19888, effective(4294967294, 4294967294), real(0, 0)] locking/locking_shm.c:shm_set_share_mode(456) set_share_mode: Created share record for test.sh (dev a0007 inode 8193) [2005/04/22 12:21:36.364683, 3, pid=19888, effective(4294967294, 4294967294), real(0, 0)] locking/locking_shm.c:shm_set_share_mode(495) set_share_mode: Created share entry for test.sh with mode 0x21 pid=19888 [2005/04/...

...: Volker Lendecke <vl at samba.org> Date: Mon Sep 16 16:16:40 2019 -0700 smbd: Don't always walk the share mode array in open_mode_check() share_mode_data->flags contains the "most restrictive" share mode of the whole array. This is maintained lazily: Whenever set_share_mode() is called, d->flags is updated if the new share mode got more restrictive. It is not updated when a file is closed, as this would mean we would have to walk the whole array, making sure that the closed handle was indeed the only most restrictive one. Instead, we walk the sh...