The problem with the sticky bit is solved. According to me it is working now. But I noticed an other strange thing. I've upgraded samba from 2.0.7 > 2.2.2 But when I have made a directory in windows and I delete that directory in the left side of the windows explorer, it will not delete. When I do this twice it is deleted. When I delete the directory at the right side of the windows explorer, there is no problem. When I use samba 2.0.7 it works also every time. What do I wrong in the conf of samba 2.2.2 or is it a bug?
On Thu, 25 Oct 2001, Martin Stuij wrote:> But I noticed an other strange thing. > > I've upgraded samba from 2.0.7 > 2.2.2 > > But when I have made a directory in windows and I delete that directory in > the left side of the windows explorer, it will not delete. When I do this > twice it is deleted. > > When I delete the directory at the right side of the windows explorer, there > is no problem. > > When I use samba 2.0.7 it works also every time. > > What do I wrong in the conf of samba 2.2.2 or is it a bug? >I believe I've seen this bug too. However, I have a different interpretation of why it happens. I've submitted a bug report at the following http://bugs.samba.org/cgi-bin/samba-bugs/incoming?id=21897;user=guest I believe this bug occurs when you try to delete a directory which has opened subdirectories. Furthermore, it only occurs on Windows 2000 on Samba-2.2.x. I've tested Samba-2.0.10 and it doesn't seem to have this bug. Can you confirm that this bug only occurs with W2K clients please? Can you also confirm that it isn't with Windows Explorer per sec, but with opened subdirectories? Thanks Eddie PS Does anybody know where old versions of Samba source kept. I had difficulty tracking down old pristine releases of Samba.
> I've also had difficulty getting W98 to see updated versions of files when > the modifications have originated at other smb clients or the Linuxconsole.> > I put it down to newbieness infecting a config somewhere, and added it toa> long list of such issues which are steadily evaporating as the newbieness > fades. But maybe this one's real?Yep, yep yep hang on. I think I have a related problem that I dumped by the wayside a long time ago because I just couldn't get it to work. I had a diald monitoring program logging into a straight text file on a /home/shared public share from within Linux. The idea was that Winblows clients would poll this text file, updating it every so often within windows memory to show latest throughput statistics. The logging was working perfectly. I could easily 'tail-f' the file and see it grow for testing purposes on the Linux box. However the Winbloze clients would load the file correctly always first thing in the morning. I had set the logger to pass values into the text file at one minute intervals, and I set the clients up to parse the text file every 10 or so (a refresh basically). In code on the clients this was done as such every 10 minutes: 1> Open the text file. 2> Parse statistics 3> Close the text file and after a while of fighting with it I even did: 4> Drop any file handles etc. Just to try to get it to work. No go. The file would not re-load WITH the new information. It would always re-load (bad terminology - it obviously didn't really re-load but you get the picture) the file as it was first thing in the morning. No matter how much more info was supposed to be in it. I dumped the project with a 'too hard' sticker on it. I was a newbie at the time too. Maybe it wasn't my fault? What am I missing? Is there a real problem? -- Edward Dekkers (Director) Triple D Computer Services Pty. Ltd. 822 Rowley Road Oakford W.A. 6121 +61 8 9397-1040 ABN: 33 635 238 024