[MLUG] anything better than "man -k" (was about tmpfile)

[Jonathan King <EMAIL:PROTECTED>]

On Tue, 11 Jun 2002, Mark Haidekker wrote:

> On Tuesday 11 June 2002 01:59 pm, you wrote:
> > On Tue, 11 Jun 2002, Mike Miller wrote:
> > > What do people do in C programming (for example) in writing temp files to
> > > avoid conflicts when multiple instances of the program run
> > > simultaneously? Do you make up some random string, or use the system
> > > clock to get a string?  What's a conventional approach to this?
> >
> > Have you tried:
> >
> >    man 3 tmpfile
> >
> > and found it (or the friends mentioned) didn't do what you wanted?
> >
> > jking
> 
> Whew. There it is. I knew it. The tmpnam() function returns a valid, but 
> random,  file name. See man 3 tmpnam.

OK, so this brings up an annoyance that should be solvable somehow, 
but I don't think has been yet.  Briefly, "man -k" should be way 
more useful than it actually turns out to be.  So "man -k temporary" 
would work great for this particular question, but "man -k temp" 
comes up with a bunch of junk (based on template classes in a bunch 
of installed libraries) and the real answer buried within.

Any hints on this?

jking


--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/