hst: expose scheduling priority
All checks were successful
Test / ShareFS (push) Successful in 43s
Test / Hakurei (push) Successful in 53s
Test / Sandbox (push) Successful in 49s
Test / Sandbox (race detector) (push) Successful in 48s
Test / Hakurei (race detector) (push) Successful in 53s
Test / Create distribution (push) Successful in 35s
Test / Flake checks (push) Successful in 1m18s
All checks were successful
Test / ShareFS (push) Successful in 43s
Test / Hakurei (push) Successful in 53s
Test / Sandbox (push) Successful in 49s
Test / Sandbox (race detector) (push) Successful in 48s
Test / Hakurei (race detector) (push) Successful in 53s
Test / Create distribution (push) Successful in 35s
Test / Flake checks (push) Successful in 1m18s
This is useful when limits are configured to allow it. Signed-off-by: Ophestra <cat@gensokyo.uk>
This commit is contained in:
@@ -253,6 +253,13 @@ in
|
||||
The zero value retains the current scheduling policy.
|
||||
'';
|
||||
};
|
||||
schedPriority = mkOption {
|
||||
type = nullOr (ints.between 1 99);
|
||||
default = null;
|
||||
description = ''
|
||||
Scheduling priority to set for the container.
|
||||
'';
|
||||
};
|
||||
|
||||
nix = mkEnableOption "nix daemon access";
|
||||
mapRealUid = mkEnableOption "mapping to priv-user uid";
|
||||
|
||||
Reference in New Issue
Block a user