ugh.book

On-line Documentation 47

Waitaminit. There’s no lockf.3 man page on system? Time to try
going around the problem: send mail to a regular user of the machine.
He replies that he doesn't know where the man page is, but he gets it
when he types “man lockf.” The elements of his MANPATH are less
than helpful, as his MANPATH is a subset of mine.

So I try something other than the brute-force method:

michael: strings `which man` | grep "/" | more

/usr/catman:/usr/man

michael:

Aha! /usr/catman! A directory not in my MANPATH! Now to drop
by and see if lockf is in there.

michael: cd /usr/catman

michael: ls

a_man

g_man

local

p_man

u_man

whatis

System V default format sucks. What the hell is going on?

michael: ls -d */cat3

g_man/cat3

p_man/cat3

michael: cd g_man/cat3

michael: ls

standard

michael: cd standard

michael: ls

Bingo! The files scroll off the screen, due to rampant SysV-ism of /
bin/ls. Better to just ls a few files instead:

michael: ls lock*

No match.

michael: cd ../../../p_man/cat3

michael: ls

I luck out, and see a directory named “standard” at the top of my
xterm, which the files have again scrolled off the screen...