I believe it is a bug causing OS processes invoked from "low" priority jobs with "high" priority. I can suggest the following workaround: Download SetPriority Utility here and save in 24x7 directory
http://www.softtreetech.com/24x7/extras/setpriority.exe For example, you if you want to run notepad.exe as a low priority process, define a JAL script job with the following code
Dim PID, number
Run "notepad.exe", "", PID
Dim command, string
ConcatEx "SetPriority ", PID, " 1", command
Run command, "", PID : When I define a job as having either low or high priority I expect the
: started program to have the same priority or the default priority. : What I see happening in reality is that the started program has
: windows prority high when the job priority is set to either high or low. : If the job priority is set to normal then the priority of the started
: program also is normal. : This bug is present in 24x7 3.4.5 but also in 3.4.26 : how can I start the program with windows priority low?
|
