>>>>> "MvL" == Martin v Loewis <martin@v.loewis.de> writes:
MvL> Every time I tried to setup such a scheme, I found that it
MvL> would deadlock: while the loginfo code runs, the committer
MvL> still holds the lock. Then, the trigger would initiate code
MvL> on the remote machine, which in turn tries a CVS update. That
MvL> will then wait for the lock.
MvL> How do you solve this problem?
syncmail has the same problem; it solves it by forking() a child
process which waits a second or two. Sucks, but I know of no other
way.
-Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4