I have been messing with this and it seems to work, but I would like to hear if it does or not from the people that have created it. On a WindowsNT machine I have three directories shared out READONLY. These three directories are mapped to users machines and then they run programs out of them. There are ALWAYS people using files in here. At times I have to update the programs in there and I need to overwrite the files that are in there. Now on this windowsNT machine I cannot seem to do that without killing all of the connections and doing it because they are locked due to people using them. Same situation but with SAMBA on a linux machine this time. I have tried a few times and it seems to have no problem overwriting the copies that are on disk while people are still using them (at one point I actually deleted all of the files in there and it didn't complain). Is it true that SAMBA will allow this or have I just been lucky so far? Brent Norris Net-Tech:BG-AFNI
Hello Brent, The deal is, that you are accessing/deleting the files from LINUX, and the users are accessingthem thru samba. Depending on how you have certain locking parameters defined in your smb.conf file (oplocks, locking, strict locking), the pc useage of the files on this disk does not 'bleed' down to the LINUX level, so linux doesn't know (or care) that someone is using them; esp when a client is using a file with an oplock, that typically ONLY samba is keeping track of. As long as the files that you are updating are executables, and you don't have to worry about data corruption, this is probably just fine. You MIGHT run into an issue if you are in the middle of an update while people are using these programs in that they might get mixed revs of the main programs and/or some dlls, but that's up to you. Hope this helps, Don -----Original Message----- From: BRENTNORRIS@afninet.com [mailto:BRENTNORRIS@afninet.com] Sent: Friday, November 09, 2001 8:17 AM To: samba@samba.org Subject: Open Files I have been messing with this and it seems to work, but I would like to hear if it does or not from the people that have created it. On a WindowsNT machine I have three directories shared out READONLY. These three directories are mapped to users machines and then they run programs out of them. There are ALWAYS people using files in here. At times I have to update the programs in there and I need to overwrite the files that are in there. Now on this windowsNT machine I cannot seem to do that without killing all of the connections and doing it because they are locked due to people using them. Same situation but with SAMBA on a linux machine this time. I have tried a few times and it seems to have no problem overwriting the copies that are on disk while people are still using them (at one point I actually deleted all of the files in there and it didn't complain). Is it true that SAMBA will allow this or have I just been lucky so far? Brent Norris Net-Tech:BG-AFNI -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Howdy,>On a WindowsNT machine I have three directories shared out READONLY. These >three directories are mapped to users machines and then they run programs >out of them. There are ALWAYS people using files in here. At times I have >to update the programs in there and I need to overwrite the files that are >in there. Now on this windowsNT machine I cannot seem to do that without >killing all of the connections and doing it because they are locked due to >people using them. > >Same situation but with SAMBA on a linux machine this time. I have tried a >few times and it seems to have no problem overwriting the copies that are on >disk while people are still using them (at one point I actually deleted all >of the files in there and it didn't complain). Is it true that SAMBA will >allow this or have I just been lucky so far?Another thing that might just be saving you from grief (as well as oplocks mentioned another reply to your message) is the fact that in UNIX, generally speaking, deleting an open file does not cause it to be removed from disk, until the last process with the file open finishes using the file. Even creating a new file with the same name doesn't break this, as the system can distinguish between a recently-deleted-but-still-open 'file.exe' and a newly created 'file.exe'. I'm not sure this is really helping you all that much as Windows clients tend to open files, read bits, close the file and then re-open it later to read some more. If you deleted the file during the first open and replaced it with a new one before the second open you might get a problem. This probably applies less to executables though. Mac Assistant Systems Adminstrator @nibsc.ac.uk dmccann@nibsc.ac.uk Work: +44 1707 654753 x285 Everything else: +44 7956 237670 (anytime)