Subj : crashmail Echo JAM Base - Errors and Exporting
To   : Bj”rn Felten
From : mark lewis
Date : Sun Oct 30 2016 05:13:46


30 Oct 16 03:00, you wrote to Richard Menedetter:

 RM>> I use JAM exclusively, and Golded+ never corrupted anything here.

 BF>    The question is what happens when another program (such as crashmail)
 BF> accesses the same JAM file.

that shouldn't be a problem in most cases...

 BF> crashmail uses it's own rudimentary lock function, with a lock file,
 BF> preventing it from having multiple runs at the same time (happens

that's normal for most tossers that i'm aware of...

 BF> quite often here) writing to the same JAM file.

JAM has its own special lock method, too... i forget which file it is but there's a region that is locked during writing... reading is allowed by all... if something else wants to write, it tries to lock the same region... if it cannot, which it should not because of the existing lock, then it should delay and retry the lock for some period of time... if it gets the lock, then it can do its write... otherwise it either aborts or asks the operator what to do...

 BF>    I guess Golded don't respect the crashmail busy file?  8-)

maybe, maybe not... depends on the config, i guess...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
.... Next! Next! Number 17! Number 17!
---
 * Origin:  (1:3634/12.73)

.