[DragonFlyBSD - Bug #3331] dsynth timeout and limits

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Mon Nov 7 01:22:13 PST 2022


Задача #3331 була оновлена arcade at b1t.name.


There's a 15 minute timeout for a job activity, if there are no new lines in the log during that period job is dropped.

----------------------------------------
Bug #3331: dsynth timeout and limits
http://bugs.dragonflybsd.org/issues/3331#change-14415

* Автор: arcade at b1t.name
* Статус: In Progress
* Пріоритет: Normal
* Версія: 6.4
* Початок: 2022-09-26
----------------------------------------
Hello.

Watching dsynth I often see that it wants to limit number of running jobs, but actually it just prevents new jobs starting. Also under huge load like building other packages sitting in swap jobs can timeout.

For example build reaches chromium while building something huge like firefox with almost no free mem. This means extracting chromium we would need to write a lot of data to swap while reading it from disk and other build also will be swapping a lot. For me it can take more then 15 minutes sometimes.

It would be really nice that this timeout could be configurable.

Also on the limits: it's really easy to suspend any job by `kill -17 -JOB_PID`, this will make all process group STOP for now. Later it can be resumed with -19.

Big thanks in advance, hope this can be interesting as an improvement.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


More information about the Bugs mailing list