Closed techsy730 closed 2 years ago
Seems to have been introduced in 1dfae65f973f8ed455734b8315bd000ca2cf38ea
When looping over background processes, it now performs config.background.unwrap_or(0)
, instead of matching config.background
against a Some
(and thus breaking out if it was None
)
If the concern is about processes that go from foreground -> background keeping their foreground priority, then maybe the configuration can error, or warn, if background is None but foreground isn't.
When setting in the config.ron
system76-scheduler now interprets that as a niceness of 0, instead of leaving it unchanged for background processes.
still seems to work as intended (configures it not to change priorities)