Update of /home/halls/cvs/debian-openoffice/oo-debian-files/doc
In directory gluck:/tmp/cvs-serv31628/doc
Modified Files:
README.Debian
Log Message:
* If setup fails, report error code to stderr
* Detect .lock that indicates that OOo is already running,
and do not attempt to run setup if found (Closes: #241224)
* doc/README.Debian: Add advice about checking for lockd when using
NFS filesystems
* debian/control: Update dependencies to require openoffice >> 1.1.1
Index: README.Debian
===================================================================
RCS file: /home/halls/cvs/debian-openoffice/oo-debian-files/doc/README.Debian,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- README.Debian 22 Feb 2004 14:15:55 -0000 1.35
+++ README.Debian 16 Apr 2004 21:51:37 -0000 1.36
@@ -172,7 +172,23 @@
Try moving that file away temporarily to see if it is the cause of the crash.
If you do not get such a message, see the next item.
-3. You may be able to provide us with information about the crash by producing
+3. If you are using NFS mounted file systems, you should make sure that locking
+is functioning:
+
+ 'Make sure NFS lockd is running on the client, or mount the NFS export which
+ contains /usr with the 'nolock' option.
+
+ If /usr gets mounted from an initrd, check 'ps' output once the system is
+ fully booted to ensure that you see a [lockd] kernel process, or an
+ 'rpc.lockd' userspace process.
+
+ If not, just issue your mount command again (no need to even -o remount it
+ seems!) and run /etc/init.d/nfs-common restart.' (Thanks to Gavin Hamill)
+
+ See this mailing list thread for more information:
+
http://lists.debian.org/debian-openoffice/2004/debian-openoffice-200402/msg00223.html
+
+4. You may be able to provide us with information about the crash by producing
a core dump. Make sure you are in a directory where you have write permission,
and execute this:
