Linux Red Hat Enterprise AS 3

I'm running an image from an NFS-mounted filesystem, which is
attempting to lock/unlock records in a POSIX shared memory segment in
/dev/shm on the local machine.

I'm getting "No locks available" instead of the happiness that
happens when I run the image from a local filesystem.  I'm reading
Steven's APUE sec. 12.3 right now, but if there are other references
(or discussion) that can hasten me to a solution I'd be grateful.

[ Post a follow-up to this message ]

entr@py.invalid wrote...
> Linux Red Hat Enterprise AS 3
>
> I'm running an image from an NFS-mounted filesystem, which is
> attempting to lock/unlock records in a POSIX shared memory segment in
> /dev/shm on the local machine.
>
> I'm getting "No locks available" instead of the happiness that
> happens when I run the image from a local filesystem.  I'm reading
> Steven's APUE sec. 12.3 right now, but if there are other references
> (or discussion) that can hasten me to a solution I'd be grateful.

BTW, I'm using fcntl() for this, not flock().

[ Post a follow-up to this message ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

entropy <entr@py.invalid> writes:

> entr@py.invalid wrote... 
>
> BTW, I'm using fcntl() for this, not flock().

Good!

You need to make sure that both the client and server are running
lockd, and that both the client and server lockds can communicate.
Check your logs, and hosts.allow|deny.


- --
Roger Leigh
Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
Debian GNU/Linux        http://www.debian.org/
GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFClkiOVcFcaSW/uEgRAhfMAKCzlnDteGzjBw98tDfUiqkTZDBc/wCgmbkH
tqubuBXC/cEM5FmuDdo2F7o=
=IQmP
-----END PGP SIGNATURE-----

[ Post a follow-up to this message ]

${rleigh}@invalid.whinlatter.ukfsn.org.invalid wrote...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> entropy <entr@py.invalid> writes:
> 
>
> Good!
>
> You need to make sure that both the client and server are running
> lockd, and that both the client and server lockds can communicate.
> Check your logs, and hosts.allow|deny.

Lockd is indeed running on both client and server, logs are clean,
and hosts.allow|deny don't seem to be at fault.  I've also pissed off
the ever-sensitive SAs now too, by implying something's wrong with
NFS that they don't know about.  

[ Post a follow-up to this message ]