Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#132 Need a DirLock parameter to choose lock directory

open
nobody
None
5
2012-10-11
2002-09-03
Carl A. Dunham
No

Currently, $DirLock is set to either the value of the
TEMP (or TMP) environment variable, or "/tmp".

For shared-hosting systems, this creates a couple of
nasty problems, one of which is that errant lock files
may block execution for every host on the system, and
the one who created the lock may not have sufficient
permissions to delete it! Also, if any two hosts run an
update at the same time, one will be unnecessarily blocked.

In general, the use of files in world-readable
locations if frowned upon. In this case, probably the
worst that could happen is that any user could block
updates for the entire system.

Would like to see a different directory used, and/or be
able to specify the lock file and dir in the config file.

Discussion

  • Logged In: YES
    user_id=96898

    The lock is not enabled by default.
    Keep EnableLockForUpdate to 0 in config file.

    Note that with several host you have several config files
    and the lock contains the name of the config files so locks must
    be different for each host if you enable it.

    DirLock parameter will be added later.