There are two timeout options in the repository options, one for the housecleaning and one for the dependency handling. The default is 300 seconds. I dont think any of these settings work to be honest, i didnt even realize these timeouts existed as we never saw the processes be killed if they went long
Thanks for reporting this! We’ve logged this as a bug and will look into it.
Cheers,
Ryan
At least on Linux, these processes almost always hang and pile up. The only “safe” way to go is to disable running all the operations as separate processes.
We are running them on linux as separate processes, and they are more or less reliable. The lock files stop ‘new’ ones from starting in most cases, although i do find duplicates from time to time.
When we had them run in the same process, we had extreme reliability problems with pulse (at one point had a cronjob that would restart pulse every 2 mins…)