Hi
This change is wrong. ABOVE_NORMAL_PRIORITY_CLASS sets them to a process level of 10 which
is too high.
Windows actually runs these at a level of 9 to ensure they get proc time before the
regular NORMAL_PRIORITY_CLASS(8) processes but below the ABOVE_NORMAL_PRIORITY_CLASS(10)
processes.
IIRC, you should be able to set the process directly using NtSetInformationProcess
although our implementation doesn't seem to reflect this.
Is it our implementation or my memory which is wrong ?
Ged.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of
dchapyshev(a)svn.reactos.org
Sent: 12 June 2009 16:41
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [dchapyshev] 41389: - Start services.exe and lsass.exe with above
normal priority class
Author: dchapyshev
Date: Fri Jun 12 19:41:26 2009
New Revision: 41389
URL:
http://svn.reactos.org/svn/reactos?rev=41389&view=rev
Log:
- Start services.exe and lsass.exe with above normal priority class
Modified:
trunk/reactos/base/system/winlogon/winlogon.c
Modified: trunk/reactos/base/system/winlogon/winlogon.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/base/system/winlogon/winlo…
==============================================================================
--- trunk/reactos/base/system/winlogon/winlogon.c [iso-8859-1] (original)
+++ trunk/reactos/base/system/winlogon/winlogon.c [iso-8859-1] Fri Jun 12 19:41:26 2009
@@ -49,7 +49,7 @@
NULL,
NULL,
FALSE,
- DETACHED_PROCESS,
+ DETACHED_PROCESS | ABOVE_NORMAL_PRIORITY_CLASS,
NULL,
NULL,
&StartupInfo,
@@ -97,7 +97,7 @@
NULL,
NULL,
FALSE,
- DETACHED_PROCESS,
+ DETACHED_PROCESS | ABOVE_NORMAL_PRIORITY_CLASS,
NULL,
NULL,
&StartupInfo,