I have tried the suggestions noted in prior appends, and it still does not work. I upgraded to kernel 2.2.18-21 as suggested. This did not fix the problem. I then upgraded from samba 2.0.7-21 to 2.0.7-23. This also did not help (I did not expect it to). My current system: Linux version 2.2.18pre21 (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) The basic problem: 1) start appending to a local NT file from a process running on the NT box (I used ping -t 127.0.0.1 > temp.txt) 2) "mount -t smbfs" the NT share on the linux server. 3) try "tail -f temp.txt" Tail will list the contents of the file up to the "current" end of file, and then either first report "==> test.txt: file truncated <==" or just "hang" as if no additional records were being appended to the file. If you leave it running, OCCASIONALLY you will get a PARTIAL record displayed (at random intervals) The tail output follows: Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 ==> test.txt: file truncated <=.1: bytes=32 time<10ms TTL=128 e<10ms TTL=128 0.0.1: bytes=32 time<10ms TTL=128 This problem is not limited to "tail". I have tried other applications that also can not continuously read the file as they are supposed to be able to (they work if the file is linux-local, though). Also, if you append to the NT file from the linux box then tail DOES see the change. Yet another also, if you break and then restart the appending process on NT (keeping the linux tail running) then the NT box reports: "The process cannot access the file because it is being used by another process". Seems like there is also a locking problem (I tried mounting the filesystem "ro" but that did not help either). This is a real mess. Any help would be greatly appreciated. Thanks, Jason -------------- next part -------------- HTML attachment scrubbed and removed
On Fri, 17 Nov 2000, root wrote:> 1) start appending to a local NT file from a process running on the NT > box (I used ping -t 127.0.0.1 > temp.txt)Does 'ping -t 127.0.0.1 > temp.txt' really append to temp.txt? Does it not (for each run) truncate and rewrite the file, just as tail -f on the linux side says? I don't have an NT-box handy, but in dosemu % echo hej > aa % echo hej > aa Generates a file containing only one "hej". % del aa % echo hej > aa % echo hej2 >> aa Generates a file with "hej" and "hej2". Does > vs >> make any difference for you?> Also, if you append to the NT file from the linux box then tail DOES > see the change. Yet another also, if you break and then restart the > appending process on NT (keeping the linux tail running) then the NT > box reports: "The process cannot access the file because it is being > used by another process". Seems like there is also a locking problem > (I tried mounting the filesystem "ro" but that did not help either).There are locking problems with smbfs. It sort of doesn't implement locking at all ... smbfs opens all files read-write, that may be what is blocking access for the other process. ro-mounts does not help, it still makes the same call to the other side. /Urban