Re: ifile lexing question

[email protected] writes:

> I'd create a file .idata.lock and put the socket somewhere in /tmp. 

it occured to me that some future ifile feature could want to derive
something from one database and write to another, so a separate
lockfile for protecting a database operation is well advised.  also,
it could be impossible to lock the original even when only read access
is wanted (but write access to something else).

this "something else" i find annoying to having to protect is my
accuracy file.  it isn't strictly neccessary for ifile's operation,
but i can't allow two processes write to it at the same time.  i'd
appreciate it if ifile's locking could be extended to this type of
add-on.  currently i do that with tools like lockfile (from procmail,
i think) or setlock (from some djb-related tool-set).

-- 
clemens