On Wed, Jul 16, 2003 at 11:30:30AM +0900, Joel Rees wrote:
> > Hmm. I would either think it a bug for Samba to be unable to tell
> > MSWindows that it had a file open for read, or a rather advanced
> > technique for Samba to be able to understand from simply mounting the
> > share as read-only that
> Hmm. I would either think it a bug for Samba to be unable to tell
> MSWindows that it had a file open for read, or a rather advanced
> technique for Samba to be able to understand from simply mounting the
> share as read-only that it could let MSWindows forego a lock on a
> multiply opened file.
> > >The tail -f works fine, but the application on the Windows side that should
> > >be appending data to this file (think syslog like functionality) pops up an
> > >error message about not being able to write to the file.
> > >
> > >I've mounted the share as read only,
> >
> > Um, why are you ex
On Mon, Jul 14, 2003 at 07:57:39PM -0400, Chuck Swiger wrote:
> stan wrote:
> [ ... ]
> >The tail -f works fine, but the application on the Windows side that should
> >be appending data to this file (think syslog like functionality) pops up an
> >error message about not being able to write to the f
stan wrote:
[ ... ]
The tail -f works fine, but the application on the Windows side that should
be appending data to this file (think syslog like functionality) pops up an
error message about not being able to write to the file.
I've mounted the share as read only,
Um, why are you expecting the Win
I've got a machine that I need to mount a Samba share from a Windows
machine, and run a tail -f on.
The tail -f works fine, but the application on the Windows side that should
be appending data to this file (think syslog like functionality) pops up an
error message about not being able to write t
