Bug 6594 – Server priority isn't updated on the fly

Bug 6594 - Server priority isn't updated on the fly

Summary:

Server priority isn't updated on the fly

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Platform Support
Version:	7.0
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	7.x
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-13 03:03 UTC by Jim McAtee
Modified:	2009-07-31 10:15 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jim McAtee 2008-01-13 03:03:50 UTC

Windows XP Pro SP2, SC7 r16227.

Unlike in SlimServer 6.5.5, changing the server priority in the Performance options doesn't immediately update the SC7 process's priority.  Only on restarting the server does the new priority level take effect.

I'm running the Perl code as a service using srvany (both for 6.5 and 7.0) so couldn't say for certain whether this affects the 'compiled' version of the server, either when run as a user process or as a service.  It's very easy to test, though.  Just change the priority to one of the named levels and then check the priority level in Task Manager.

Comment 1 Blackketter Dean 2008-01-14 10:09:45 UTC

Michael to investigate.

Comment 2 Michael Herger 2008-01-16 02:29:48 UTC

Punting post 7.0

Comment 3 Michael Herger 2008-02-14 01:34:10 UTC

change 17535 - change the priority after pref change

Comment 4 James Richardson 2008-05-07 10:40:45 UTC

Jim: Can you verify that this issue has been properly address for you?  If not, please reopen the bug

Comment 5 Chris Owens 2009-07-31 10:15:44 UTC

Reduce number of active targets for SC