Re: best dbm for small dictionaries? write locking or concurrency needed

A very simplicisitic approach would simply append all information to a log file and keep the reporting separate. This means that you won't really have to deal with locking as long as you append "short" lines to the logfile, as they are written atomically. Of course, the downside is that reporting about the programs becomes a bit more tedious and maybe you'll have to write a script that runs every week to prune unwanted information from the logs.

Comment on Re: best dbm for small dictionaries? write locking or concurrency needed

Replies are listed 'Best First'.
Re^2: best dbm for small dictionaries? write locking or concurrency needed by Anonymous Monk on Oct 14, 2010 at 14:47 UTC
The problem is that some programs get run frequently and some infrequently. I'd have to prune at a certain length, but the last 50k lines of output might be dominated by a single program. I guess I could prune using "uniq" to coalesce similar lines together.... not exactly what I wanted, however.	[reply]