On Wed, 2009-07-15 at 10:43 -0700, Craig White wrote:
> On Wed, 2009-07-15 at 11:02 -0400, JohnS wrote:
> > On Tue, 2009-07-14 at 06:39 -0700, Craig White wrote:
> > > On Tue, 2009-07-14 at 00:42 -0400, JohnS wrote:
> > > > On Mon, 2009-07-13 at 16:32 -0400, Rob Kampen wrote:
> > > > <snip>
> > > > >
> > > > > So now it seems what I have is an Openoffice problem. It writes odt
> > > > > files just fine via nfs but not doc files.
> > > > > Must be a micro$oft conspiracy.
> > > > > I'll take this off list as it does not appear to be a CentOS issue.
> > > > ---
> > > > /usr/lib/openoffice/program/soffice
> > > >
> > > > # file locking now enabled by default
> > > > SAL_ENABLE_FILE_LOCKING=1
> > > > export SAL_ENABLE_FILE_LOCKING
> > > >
> > > > Comment those two lines out and try that. An alternative is to use
> > > > Samba instead of NFS. I had that problem on NFS also a while ago.
> > > ----
> > > perhaps as a test but that is a bad idea for every day usage.
> > >
> > > Craig
> >
> > ---
> > Correct, but I only use that on a NFS server at home and not on
> > production client machines. Production client I have using samba.
> ----
> I can assure you from my own home usage that if I have file open on
> Linux (Fedora) desktop system, files are mounted from CentOS server via
> NFS mount and Windows uses samba from same CentOS server and if either
> is using an ODF or XLS or DOC file, the other will be notified that the
> file is locked and offered to open a copy or read-only. Locking
> semantics seems to work perfectly among systems.
>
> Craig
---
This is the older Open Office Version 2. This was not a samba or nfs
problem. Since it has been fixed in Open Office but not my end. Does
that explain my usage? I don't have the time to get to many of my own
things. :-)
John
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
