X Strike Force SVN commit: rev 356 - trunk/debian
Author: branden
Date: 2003-08-01 17:22:12 -0500 (Fri, 01 Aug 2003)
New Revision: 356
Modified:
trunk/debian/changelog
trunk/debian/xserver-common.templates
Log:
debian/xserver-common.templates: advise users of Linux with O(1) scheduler
to use a nice value of zero; also, remove the default setting for the
corresponding template so that a default is set only by the config script
Modified: trunk/debian/changelog
==============================================================================
--- trunk/debian/changelog 2003-08-01 21:34:01 UTC (rev 355)
+++ trunk/debian/changelog 2003-08-01 22:22:12 UTC (rev 356)
@@ -71,15 +71,20 @@
discover trick wc into interpreting a blank line as a detected video card
(based on a patch by Nikita V. Youshchenko -- thanks!) (Closes: #195418)
- * debian/xserver-common.config.in: if the user is running Linux > 2.5 at the
- time this package is configured for the first time, set the default nice
- value to 0 instead of -10
+ * Be cognizant of different scheduling behavior in Linux >= 2.5.
+ - debian/xserver-common.config.in: if the user is running Linux > 2.5 at
+ the time this package is configured for the first time, set the default
+ nice value to 0 instead of -10
+ - debian/xserver-common.templates: advise users of Linux with O(1)
+ scheduler to use a nice value of zero; also, remove the default setting
+ for the corresponding template so that a default is set only by the
+ config script
* debian/local/xserver-wrapper.c: chdir() to the directory where the X
server symlink is kept before executing its target, so that relative
symlinks work (Closes: #138195)
- -- Branden Robinson <branden@debian.org> Fri, 1 Aug 2003 14:23:18 -0500
+ -- Branden Robinson <branden@debian.org> Fri, 1 Aug 2003 17:19:33 -0500
xfree86 (4.2.1-9) unstable; urgency=high
Modified: trunk/debian/xserver-common.templates
==============================================================================
--- trunk/debian/xserver-common.templates 2003-08-01 21:34:01 UTC (rev 355)
+++ trunk/debian/xserver-common.templates 2003-08-01 22:22:12 UTC (rev 356)
@@ -42,19 +42,24 @@
Template: xserver-common/xwrapper/nice_value
Type: string
-Default: -10
_Description: Enter the desired nice value for the X server to use.
- It has been widely noted that the X server's performance improves if it is
- run at a higher process priority than the default; a process's priority is
- known as its "nice" value. They range from -20 (extremely high priority, or
- "not nice" to other processes) to 19 (extremely low priority). The default
- nice value for ordinary processes is 0. -10 is a good default for a
- single-user workstation; 0 is a good default for a machine that has duties
- other than interacting with the console user (such as a web server).
+ When using operating system kernels with a particular scheduling strategy,
+ it has been widely notes that the X server's performance improves when it
+ is run at a higher process priority than the default; a process's priority
+ is known as its "nice" value. They range from -20 (extremely high
+ priority, or "not nice" to other processes) to 19 (extremely low
+ priority). The default nice value for ordinary processes is 0. -10 is a
+ good default for a single-user workstation; 0 is a good default for a
+ machine that has duties other than interacting with the console user (such
+ as a web server).
.
- Values outside the range of -10 to 0 are not recommended; too low, and the X
- server will interfere with important system tasks. Too high, and the X
- server will be sluggish and unresponsive.
+ The above is not true of Linux kernel version 2.6 (nor of the 2.5 series
+ after the "O(1) scheduler" was included); on such systems, the nice value
+ of the X server should be set to 0.
+ .
+ Values outside the range of -10 to 0 are not recommended; too negative,
+ and the X server will interfere with important system tasks. Too
+ positive, and the X server will be sluggish and unresponsive.
Template: xserver-common/xwrapper/nice_value/error
Type: note
Reply to: