Joe Zeff <ahnkna...@zeff.us> wrote: > >I have, several times, caused problems by accidentally starting Pan >twice without realizing it. (Mostly, the program gets tangled up about >which articles have been read until I edit the newsrec file.) I'd like >to suggest that Pan create a file, pan.lok, in its own directory and >remove it again on exit so that you can't have two copies using the same >configuration at the same time.
Sounds like a good idea. > (For Linux, at least, you can open the >file, creating it, delete it and then close it at exit because the >delete will be delayed until after it's closed. That way, if Pan >crashes, the lock still gets removed. This is standard Unix filesystem semantics. Exploiting this functionality is counter-productive if the file is supposed to be a lock file, though. (As far as access via the filesystem is concerned, the file ceases to exist at the point of the unlink(2).) --Per Hedeland _______________________________________________ Pan-users mailing list Pan-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/pan-users
