We are in a situation where we have to use IIS to publish some documents on the web. However, these documents can currently only be generated on Unix. This is not a problem, seeing that we can just make a tar file and use smbclient in tar mode (smbtar) to move the documents to the NT server with IIS. However, there is one problem. Apparently smbclient will open the files without specifying DENY_NONE, causing a sharing violation because IIS is doing extensive caching. Replacing the file locally on the system will work, as will replacing it across the netwrok from another WinNT system. I was hoping you might have some idea on how to get around this problem. Might it be as simple as using SMBopen with DENY_NONE (or perhaps just giving the DENY_NONE flag to SMBcreat?) when trying to extract the files? Any help would be much appreciated! Thorsten
On Monday, September 29, 1997 11:21 PM, samba@samba.anu.edu.au [SMTP:samba@samba.anu.edu.au] wrote: ------------------------------> > Date: Mon, 29 Sep 1997 20:50:42 -0700 (PDT) > From: Thorsten Lockert <tholo@ebay.com> > To: samba-team@samba.anu.edu.au > Cc: samba@samba.anu.edu.au > Subject: File copying with smbclient vs. IIS > Message-ID: <199709300350.UAA23700@thompson.ebay.com> > > We are in a situation where we have to use IIS to publish some documents > on the web. However, these documents can currently only be generated on > Unix. > > This is not a problem, seeing that we can just make a tar file and use > smbclient in tar mode (smbtar) to move the documents to the NT server with > IIS. > > However, there is one problem. Apparently smbclient will open the files > without specifying DENY_NONE, causing a sharing violation because IIS is > doing extensive caching. Replacing the file locally on the system will > work, as will replacing it across the netwrok from another WinNT system. > > I was hoping you might have some idea on how to get around this problem. > Might it be as simple as using SMBopen with DENY_NONE (or perhaps just > giving the DENY_NONE flag to SMBcreat?) when trying to extract the files? > > Any help would be much appreciated! > > Thorsten >I use PWS (Personal Web Server, scaled down IIS), since I'm running NTWS, to publish some UNIX generated documents on our intranet. I first created a Samba share for the directory in which the generated documents reside. Then in PWS I created a 'virtual directory' which points to the Samba share (e.g. create share \\Unix\www, then create virtual directory '/unixweb', which is an alias for \\Unix\www). Maybe you've already tried this or there is some other reason you want to move the documents to the server, but, this works great for me. Steve Remme Storage Technology Corporation 2270 S. 88th Street, MS 2214 Louisville, CO 80028-2214 Email: RemmeSK@louisville.stortek.com Voice: (303) 673-6966 FAX: (303) 673-8641
On Tuesday, September 30, 1997 10:46 AM, Remme, Stephen K (Steve) [SMTP:RemmeSK@LOUISVILLE.STORTEK.COM] wrote:> > I use PWS (Personal Web Server, scaled down IIS), since I'm running > NTWS, to publish some UNIX generated documents on our intranet. > > I first created a Samba share for the directory in which thegenerated> documents reside. Then in PWS I created a 'virtual directory' which > points to the Samba share (e.g. create share \\Unix\www, then create > virtual directory '/unixweb', which is an alias for \\Unix\www). > > Maybe you've already tried this or there is some other reason youwant> to move the documents to the server, but, this works great for me.Yes, well, the server in question is getting on the order of 1 million hits a day, so having it get its pages across a SMB connection is really not feasible. Thorsten
Actually this is a bug of IIS, since it should be possible to edit/remove the files while the server is running. Only the one request in progress when the file is changed should be broken, but the cache would have to compare the file status. Check if you have the same behaviour if you modify the files not through network but on the server itself (using notepad or whatever). Hiran Chaudhuri Thorsten Lockert wrote:> We are in a situation where we have to use IIS to publish some > documents > on the web. However, these documents can currently only be generated > on > Unix. > > This is not a problem, seeing that we can just make a tar file and use > > smbclient in tar mode (smbtar) to move the documents to the NT server > with > IIS. > > However, there is one problem. Apparently smbclient will open the > files > without specifying DENY_NONE, causing a sharing violation because IIS > is > doing extensive caching. Replacing the file locally on the system > will > work, as will replacing it across the netwrok from another WinNT > system. > > I was hoping you might have some idea on how to get around this > problem. > Might it be as simple as using SMBopen with DENY_NONE (or perhaps just > > giving the DENY_NONE flag to SMBcreat?) when trying to extract the > files? > > Any help would be much appreciated! > > Thorsten > > ------------------------------
On Thursday, October 02, 1997 1:30 AM, Hiran Chaudhuri [SMTP:Hiran.Chaudhuri@lrz.fh-muenchen.de] wrote:> Actually this is a bug of IIS, since it should be possible to > edit/remove the files while the server is running. Only the onerequest> in progress when the file is changed should be broken, but the cache > would have to compare the file status. > > Check if you have the same behaviour if you modify the files notthrough> network but on the server itself (using notepad or whatever).Editing / renaming / removing / replacing the file locally does work. That's why I decided to cry for help. I did find a different workaround for the problem tho, which (for now) seems to work. Thorsten