Home
last modified time | relevance | path

Searched refs:adjustment (Results 1 – 5 of 5) sorted by relevance

/coreutils/src/
Dnice.c103 int adjustment = 10; in main() local
174 adjustment = MAX (MIN_ADJUSTMENT, MIN (tmp, MAX_ADJUSTMENT)); in main()
195 ok = (nice (adjustment) != -1 || errno == 0); in main()
200 ok = (setpriority (PRIO_PROCESS, 0, current_niceness + adjustment) == 0); in main()
/coreutils/tests/date/
Ddate-debug.sh49 date: after date adjustment (+0 years, +0 months, +3 days),
52 date: after time adjustment (+0 hours, -90 minutes, +0 seconds, +0 ns),
151 date: after date adjustment (+0 years, +0 months, -8 days),
178 date: after date adjustment (+0 years, -1 months, +0 days),
180 date: warning: month/year adjustment resulted in shifted dates:
209 date: after date adjustment (+0 years, +6 months, +0 days),
211 date: warning: daylight saving time changed after date adjustment
212 date: warning: month/year adjustment resulted in shifted dates:
/coreutils/tests/
Dfilefrag-extent-compare54 or die "$ME: extent counts differ, even after adjustment\n";
/coreutils/doc/
Dfdl.texi318 Make the same adjustment to the section titles in the list of
Dcoreutils.texi18368 @item -n @var{adjustment}
18369 @itemx --adjustment=@var{adjustment}
18371 @opindex --adjustment
18372 Add @var{adjustment} instead of 10 to the command's niceness. If
18373 @var{adjustment} is negative and you lack appropriate privileges,
18375 a zero adjustment.
18378 option syntax @option{-@var{adjustment}}. New scripts should use
18379 @option{-n @var{adjustment}} instead.
18418 The @var{adjustment} is relative to the current niceness. In the