Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > when you setup a lockfile, and then fork(), you could easily end up with > atexit() kicking in to remove the lockfile, before the main process has a > chance to commit. (Yes, I need to hold the lock long before the fork()). > > Any ideas how to solve the problem? Depends on the arrangement between the parent and child regarding who is responsible for unlocking. If child expects to work under the safety of the lock the parent prepared, and also relies on the parent to wait for it and then unlock to ensure that safety for the child, then I think the problem is simple. How about defining a function in lockfile.c to assign NULL to lock_file_list and call that immediately after fork() in the child? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html