Rene Engelhard wrote:
And statd?
Sorry, what do you mean exactly?
We run (almost) all our applications on files that are nfs mounted. OO
is the _one_ application that freezes on files via nfs (and doesn't
freeze, if the file is copied to a local folder).
This bug makes openoffice unusable on workstations with nfs mounted
directories.
openoffice? probably not. There's no openoffice, neither in Debian or
anywhere...
[EMAIL PROTECTED]:~$ which openoffice
/usr/bin/openoffice
[EMAIL PROTECTED]:~$ man openoffice
Reformatting openoffice(1), please wait...
Anyway, do you have statd running? If not, that's your nfs at fault.
(Of course, OOo shouldn't hang, but,..)
[EMAIL PROTECTED]:~$ ps aux |grep stat[d]
statd 4880 0.0 0.0 2648 248 ? Ss 07:26 0:00
/sbin/rpc.statd
And neither of them has a "openoffice".
Can't people finally write the programs' name as it is?
Both of them do. Can't you try a 'man openoffice' before repeatedly
arguing about it? It's not my fault that you could start the same
application via ooo-wrapper, openoffice or ooffice. I guess it was clear
about what I was talking in my mail. As to a previous report in this
thread, all applications of the openoffice.org suite seem to be
affected, so instead of listing
ooffice
oobase
oocalc
oodraw
oohtml
ooimpress
oomath
oowriter
I just wrote openoffice.
Gr��e/Regards,
Grüße aus Freising,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
