lockf in installworld -- not a good idea

[Ruslan Ermilov]

On Fri, Sep 29, 2006 at 03:19:50PM +0100, Robert Watson wrote:
> On Fri, 29 Sep 2006, Ruslan Ermilov wrote:
> >How could it support parallelism without using lockf(3) or equivalent? I'd 
> >be happy to hack install-info(1) if there's a way.
> 
> Yes, that's why it's the basic problem. :-)  The problem is the way info 
> works -- that it uses a shared file for a global table of contents, rather 
> than constructing it from a set of independent files once.  Is there any 
> way to generate the entries in the directory incrementally in different 
> files, then combine them all at the end once?  I.e., like we do with the 
> man page apropos database -- we build all the elements independently, which 
> is parallelizable, and then once at the end once it's all done, we build 
> the single central database.
> 
Nothing immediate comes to my mind, but I'll think about it more.

> >A middle-ground solution was easy to implement, and I have a patch for it 
> >if a more clean solution couldn't be found.
> 
> I'd like to see that in the tree in the near future.  If nothing else, it 
> will speed up installworld in the non-j case, probably measurably (although 
> I've not measured it :-).
> 
OK, committed to HEAD as bsd.info.mk,v 1.74.


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060929/fa0b353b/attachment.pgp