Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-05 Thread kyleki
Ramage;239632 Wrote: Installed 11/2 nightly, stop function works OK, but mysqld and mDNSResponder threads are left running (as expected?) If these processes are left running then it's not working properly. This was the whole point of bug 5620. In any of your tests, have these processes been

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-05 Thread kyleki
Fletch;239475 Wrote: Yeah, it's a race condition that probably only shows up on slow machines or virtual machines. My Fedora 7 box isn't necessarily slow and I was experiencing bug 5620 until the '-d 6' argument was added to the killproc function call. AMD Athlon(tm) XP 2200+ MemTotal:

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-05 Thread Fletch
I missed that part of Ramage's response. I'm not sure how to fix the bug if the -d option is not available. Ramage, is it repeatable? Is it running in a VM? -- Fletch Fletch's Profile:

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-02 Thread Ramage
Installed 11/2 nightly, stop function works OK: /etc/rc.d/init.d/slimserver contains: stop() { echo -n Shutting down SqueezeCenter: # Support old versions of RHEL and still fix bug 5620 KILLPROC_ARGS= if [ `grep -c 'Usage: killproc.*-d delay'

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-02 Thread Ramage
I've amended /etc/rc.d/init.d/slimserver to stop() { echo -n Shutting down SqueezeCenter: if [ `grep -c 'Usage: killproc.*-d delay' /etc/init.d/functions` -ge 1 ]; then killproc -d 6 $SLIMSERVER_BIN else killproc $SLIMSERVER_BIN

[SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
Unable to stop recent nightlies (including 1/11) using service slimserver stop. The system is CC4.1 sp1 and nightly is rpm. Other commands: start and status work OK. I get the following result on the command line: [EMAIL PROTECTED] /]# service slimserver stop Shutting down SqueezeCenter:

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
I have fixed the script for stopping SC7 in CC 4.01 sp1 Compare with the original in the first post: stop() { echo -n Shutting down SqueezeCenter: killproc $SLIMSERVER_BIN -SIGTERM RETVAL=$? echo [ $RETVAL -eq 0 ] rm -f /var/lock/subsys/slimserver return $RETVAL Note that the line

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread bpa
I think RPM build was updated recently. See http://forums.slimdevices.com/showthread.php?t=39789 -- bpa bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread:

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
bpa;239449 Wrote: I think RPM build was updated recently. See http://forums.slimdevices.com/showthread.php?t=39789 Yes I saw that and wondered if it might be the cause, but I thought the rebuilt rpm was on a separate repository accessed through yum rather than the slimserver nightlies. I

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
Ramage;239446 Wrote: I have fixed the script for stopping SC7 in CC 4.01 sp1 Compare with the original in the first post: stop() { echo -n Shutting down SqueezeCenter: killproc $SLIMSERVER_BIN -SIGTERM RETVAL=$? echo [ $RETVAL -eq 0 ] rm -f /var/lock/subsys/slimserver return

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Fletch
I made that change (change 14150) to fix bug 5620. It's been reported to work on recent versions of CentOS and Fedora. It looks like CC is incompatible with the -d option. What version of CentOS is CC4.1 based on? I'll go find a CC mirror and see why their /etc/init.d/functions is different.

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
Fletch;239468 Wrote: I made that change (change 14150) to fix bug 5620. It's been reported to work on recent versions of CentOS and Fedora. It looks like CC is incompatible with the -d option. What version of CentOS is CC4.1 based on? I'll go find a CC mirror and see why their

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Fletch
Ramage;239471 Wrote: Yeah, I've now read the bug report, but CC4.1 kills all the child processes with the old init.d Yeah, it's a race condition that probably only shows up on slow machines or virtual machines. The kernel version for CC 4.1 is 2.6.9 altho' 4.2 (now available) will upgrade

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Ramage
Thanks for the info Fletch, I'll do the workaround for now. -- Ramage T5500 1.6GHz, Slimserver 6.5.5 - 13599 - Windows Vista, Alien 1.06 P4 2.6GHz, SqueezeCentre Version: 7.0 - 14284 - Windows XP, Alien 2.0b P2 266MHz, Linux ClarkConnect 4.1.sp1, SlimServer Version: 7 - 14284, Alien 2.0b,

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Fletch
I don't know a way to test the version of the killproc() function. Something ugly like the following should work. Code: if [ `grep -c 'Usage: killproc.*-d delay' /etc/init.d/functions` -ge 1 ]; then killproc -d 6 $SLIMSERVER_BIN else killproc

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Robin Bowes
Fletch wrote: I don't know a way to test the version of the killproc() function. Something ugly like the following should work. Code: if [ `grep -c 'Usage: killproc.*-d delay' /etc/init.d/functions` -ge 1 ]; then killproc -d 6 $SLIMSERVER_BIN else

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Fletch
Yeah, that's better Robin. I wish there was a cleaner solution for if [ some_test_for_ClarkConnect ]... -- Fletch Fletch's Profile: http://forums.slimdevices.com/member.php?userid=529 View this thread:

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Robin Bowes
Fletch wrote: Yeah, that's better Robin. I wish there was a cleaner solution for if [ some_test_for_ClarkConnect ]... Check /etc/redhat-release? R. ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta

Re: [SlimDevices: Beta] Can't stop SC7 on Linux

2007-11-01 Thread Fletch
Robin Bowes;239547 Wrote: Check /etc/redhat-release? That won't work. CC 4.2 identifies itself as CentOS 4.4 which should work but doesn't. Anyway, I've committed change 14309 so it's gets in the nightly builds. Ramage, please let me know if it works OK. -- Fletch