In article <199512191647.IAA00190@lestat.nas.nasa.gov>,
Jason Thorpe  <thorpej@nas.nasa.gov> wrote:
> Well, then you might consider a shorter name.  I'm not sure how we can 
> really avoid the long manpage names if that's really the name of the 
> function :-)
> 
> Shutdown hooks aren't the only ones.  Typically, interrupt hook routines 
> have long names (like vmeintr_establish()).  The sparc also has the 
> `bootpath' functions (like bootpath_restore()) that are worth documenting.

How about grouping related functions together, and having
"shutdownhook", "vmeintr", "bootpath", etc. manual pages? I'd probably
want to read about related families of functions at the same time
anyway. The section 3 manual pages also do this.