Date: Sun, 25 Jun 2006 14:40:21 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> Cc: freebsd-arch@freebsd.org Subject: Re: What's up with our stdout? Message-ID: <20060625214021.GJ82074@funkthat.com> In-Reply-To: <20060625011746.GC81052@duncan.reilly.home> References: <20060625011746.GC81052@duncan.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Reilly wrote this message on Sun, Jun 25, 2006 at 11:17 +1000: > One interesting problem that I found yesterday was that NetBSD > have added a "-l" option to cat, which is supposed to apply an > exclusive advisory lock with fcntl to the the output file, and > wait until that succeeds: > http://netbsd.gw.com/cgi-bin/man-cgi?cat++NetBSD-current > That seems like a pretty useful idea, > because it means that you can have parallel make jobs all > contributing to a log file or the like (with cat -l >> foo.log), > without getting in eachothers' way. Why not use: lockf -k foo.log cat >> foo.log Should do the same thing... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060625214021.GJ82074>