openoffice, nfs, and long pipe name

[Elizabeth Barham <lizzy@soggytrousers.net>]

Hi,

   I recently installed openoffice.org_1.0.3-2 on two different intel
machines but one is a diskless client (its root partition is a mounted
NFS filesystem). On the non-diskless client, the new openoffice runs
well. Unfortunately, things aren't so great with the diskless machine
and I'm able to track down the error to a named socket openoffice
creates in the /tmp directory.

   The problem is that OpenOffice refers to a pipe that is 68
characters long:

  /tmp/OSL_PIPE_1001_SingleOfficeIPC_26a5989952d9fc93cdba6d37ffcb56ce

but the pipe on the filesystem itself is:

  /tmp/OSL_PIPE_1001_SingleOfficeIPC_26a5989952d9fc93cdba6d37ffcb

which is exactly 64 characters long. So, what ends up happening is
this:

access("/tmp", W_OK)                    = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 12
fcntl64(12, F_GETFD)                    = 0
fcntl64(12, F_SETFD, FD_CLOEXEC)        = 0
access("/tmp/OSL_PIPE_1001_SingleOfficeIPC_26a5989952d9fc93cdba6d37ffcb56ce", F_OK) = -1 ENOENT (No such file or directory)
close(12)                               = 0
nanosleep({0, 10000000}, NULL)          = 0
[ repeats ]
^C

   Looking at nfs3.h and limits.h, we find that the maximum file
length is 255 characters so that doesn't seem to play a role and I can
even touch the file or make a named socket:

touch /tmp/OSL_PIPE_1001_SingleOfficeIPC_26a5989952d9fc93cdba6d37ffcb56ce
mknod /tmp/OSL_PIPE_1001_SingleOfficeIPC_26a5989952d9fc93cdba6d37ffcb56ce p

but, regardless, I keep having the error on the diskless client.

   Any ideas on how to solve this problem or where to look next?

   Thank you,
   Elizabeth