showlock/lock.info on 5.7?

[Kenneth Brody]

On 7/23/2014 12:37 PM, Jay Ashworth wrote:
> I've just needed to try to figure out which dclerk was locking
> a record (note to Ken: modifying dclerk to adjust its argv[0] to say
> which file and record are open would be *really* cool :-), and discovered
> that neither works:
>
> $ showlock ml4
> returns
> ml4: Permission denied

Showlock needs the name/path of the file you want to show locks on.  For 
example:

     showlock /appl/filepro/ml4/key

I believe you want "lock.info ml4".

> whether I am a user, root, or filepro; all files in the directory, and
> the directory chain itself, are mode 777.
>
> lock.info, for its part, complains that it can't find the filepro programs;
> /appl/fp is a symlink to /appl/fp_5.7yadayada, and /appl/fp/dclerk works.

What is the exact error?  (Note that, as I recall, lock.info was written by 
a third party -- Bob Stockler, I believe?)

A quick look seems to show that $PFPROG/fp must be a directory:

    [[ -d ${PFPROG=${FP[1]))/fp ]]

A quick test here shows that the above works for symlinks to directories. 
What O/S are you on?  If you run "/bin/ksh" and type this line, what happens?

    [[ -d /appl/fp ]] || echo "Sorry"

If it shows "Sorry", then your system doesn't test symlinks to directories 
as being directories.

> Did 5.7 ship with a working showlock?  Is there any way to tell whether
> the one I'm using is the right one?
>
> What might be causing these failures?


-- 
Kenneth Brody