I am trying to get two WFW PC's talking to via Linux/Samba server Interface.
One PC continuously streams binary datafile onto its directory on the server
while the other continuously reads it. Information on the size of this file
(which can continuously increase up to 3MB) is continuously updated and is
stored using a fixed width pointer in the file header.
It appears that the second PC can't read this pointer and uses its old
value.
Therefore it can not read the file beyond its old time mark.
Everything works OK when PC's talk directly to each other (peer-to-peer)
without the server. I've tried all the usual fixes with oplocks, permissons,
etc. in smb.conf but without much success.
Is there possibly a way to force an update of the first chunk of data in the
cache?
Any help is greatly appreciated
Sergei Schurov
____________________________________________________________________
More than just email--Get your FREE Netscape WebMail account today at
http://home.netscape.com/netcenter/mail
> I am trying to get two WFW PC's talking to via Linux/Samba server Interface. > One PC continuously streams binary datafile onto its directory on the server > while the other continuously reads it. Information on the size of this file > (which can continuously increase up to 3MB) is continuously updated and is > stored using a fixed width pointer in the file header. > It appears that the second PC can't read this pointer and uses its old value. > Therefore it can not read the file beyond its old time mark. > > Everything works OK when PC's talk directly to each other (peer-to-peer) > without the server. I've tried all the usual fixes with oplocks, permissons, > etc. in smb.conf but without much success. > > Is there possibly a way to force an update of the first chunk of data in the > cache? > > Any help is greatly appreciated > Sergei SchurovHi This could (I'm not sure) also be a "problem" of linu, because it is not designed for two processes writing&reading from/to the same file. May don't you use a fifo instead of a normal file on the linux side? (check to manpage of mknod). mfg, fgp
Hello, At 04.16 12/12/98 +1100, Florian G. Pflug wrote:>This could (I'm not sure) also be a "problem" of linu, because it is not >designed for two processes writing&reading from/to the same file. May don't >you use a fifo instead of a normal file on the linux side? (check to manpage >of mknod).AFAIK Linux is POSIX compliant on this side i.e. anything that is written before a read should be seen by the reading process. Of course may be a Linux bug. Bye! Sbragion Denis InfoTecna Tel, Fax: +39 039 2324054 URL: http://space.tin.it/internet/dsbragio
On Sat, 12 Dec 1998 Sergei Schurov <sms1001@netscape.net> wrote:> I've tried all the usual fixes with oplocks, permissons, > etc. in smb.conf but without much success.When you say that you've tried oplocks do you mean that you've tried turning them off? oplocks being on can cause this sort of problem.> Sergei SchurovBrett /) _ _ _/_/ / / / _ _// /_)/</= / / (_(_/()/< /// Silicon Graphics Inc. brettw@sgi.com +61 2 6270 8707