Gentoo Archives: gentoo-amd64

From: "Nicolas MASSÉ" <nicolas27.masse@×××××××.net>
To: gentoo-amd64@l.g.o
Cc: Mark Knecht <markknecht@×××××.com>
Subject: Fwd: [gentoo-amd64] Re: Open Office / NFS write problem
Date: Tue, 28 Feb 2006 10:33:01
Message-Id: 200602272256.23560.nicolas27.masse@laposte.net
1 I had the same problem on Mac OS X, I solved it when I commented out the two
2 following lines :
3
4 SAL_ENABLE_FILE_LOCKING="0 ou 1"
5 export SAL_ENABLE_FILE_LOCKING
6
7 in "program/soffice"
8
9 You can see [1] (in french) for more details.
10
11 Best regards,
12
13 Nicolas MASSE
14
15 [1] http://forums.macgeneration.com/vbulletin/showthread.php?t=121426
16
17 ---------- Forwarded Message ----------
18
19 Subject: [gentoo-amd64] Re: Open Office / NFS write problem
20 Date: Monday 27 February 2006 01:51
21 From: "Mark Knecht" <markknecht@×××××.com>
22 To: gentoo-amd64@l.g.o
23
24 On 2/26/06, Mark Knecht <markknecht@×××××.com> wrote:
25 > Hi,
26 > I'm running Open Office on my AMD64 machine. In all ways it seems
27 > to work fine when using local hard drives. However, if I try to write
28 > any file held on my file server then I receive a message that says:
29 >
30 > Error saving the document Untitled1:
31 > General input/output error while accessing /video/Mark/test1
32 >
33 > The document was started as a new document, hence the 'Untitled1' name
34 > and I gave it the name test1 in the 'Save as...' dialog.
35 >
36 > I do not have this problem when editing from my 32-bit Gentoo
37 > machine. It's only from this AMD64 box.
38 >
39 > Is this a problem that's known already? I find this message in a
40 > few files through Google but I haven't found a clear description of
41 > why it happens or how to fix it.
42 >
43 > Could this be due to using the binary version of Open Office? I'd
44 > hate to have to build it from scratch!
45 >
46 > The NFS drive is mounted at boot time. Here's the command in my fstab
47 > file:
48 >
49 > mark@lightning ~ $ cat /etc/fstab | grep video
50 > myth14:/video /video nfs
51 > auto,user,rw,_netdev,noatime,hard,tcp,wsize=32768,rsize=8192,nfsvers=3,asyn
52 >c 0 0
53 > mark@lightning ~ $
54 >
55 > Thanks in advance,
56 > Mark
57
58 Later in my searches I found this thread at the Open Office site:
59
60 http://www.openoffice.org/issues/show_bug.cgi?id=36634
61
62 Indeed the issue at the bottom - different kernels, etc., may apply.
63
64 Our NFS Server is a MythTV frontend only machine that has a large
65 drive so we exported that drive to the network as extra storage for
66 easy backups and sharing. That machine runs an older kernel:
67
68 myth14 ~ # uname -a
69 Linux myth14 2.6.12-gentoo-r6 #2 Tue Aug 2 16:31:31 PDT 2005 i686
70 Intel(R) Celeron(R) CPU 2.26GHz GenuineIntel GNU/Linux
71 myth14 ~ #
72
73 The drive is exported as follows:
74
75 myth14 ~ # cat /etc/exports
76 # /etc/exports: NFS file systems being exported. See exports(5).
77 /video
78 192.168.1.0/255.255.255.0(rw,no_root_squash,insecure,async,no_subtree_check)
79 myth14 ~ #
80
81 My local AMD64 machine is running a newer non-Gentoo kernel:
82
83 mark@lightning ~ $ uname -a
84 Linux lightning 2.6.15-rt2 #2 PREEMPT Thu Jan 5 16:13:25 PST 2006
85 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
86 mark@lightning ~ $
87
88 Both machines run the same version of nfs-utils:
89
90 myth14 ~ # emerge -pv nfs-utils
91
92 These are the packages that I would merge, in order:
93
94 Calculating dependencies ...done!
95 [ebuild R ] net-fs/nfs-utils-1.0.6-r6 +tcpd 0 kB
96
97 Total size of downloads: 0 kB
98 myth14 ~ #
99
100 lightning ~ # emerge -pv nfs-utils
101
102 These are the packages that I would merge, in order:
103
104 Calculating dependencies ...done!
105 [ebuild R ] net-fs/nfs-utils-1.0.6-r6 +tcpd 0 kB
106
107 Total size of downloads: 0 kB
108 lightning ~ #
109
110 Thanks in advance for any ideas you can lend,
111 Mark
112
113 --
114 gentoo-amd64@g.o mailing list
115
116 -------------------------------------------------------
117 --
118 gentoo-amd64@g.o mailing list

Replies

Subject Author
Re: [gentoo-amd64] Re: Open Office / NFS write problem Mark Knecht <markknecht@×××××.com>