I installed the latest nightly build on a fresh SUSE 10.2 system last night and thought I'd share my experience for those who might be attempting something similar.
First, I downloaded the latest nightly RPM file and used RPM to install it. That went OK, except for the startup, which failed. But I was expecting that, since the RPM contains an init script for Redhat which doesn't work on SuSE. I'd previously investigated all the run scripts in the Wiki when I diagnosed some 'permissions problems' (http://forums.slimdevices.com/showthread.php?t=32200) at startup on my old system. Because I wasn't sure about using the 9.1 script on 10.2 and the 10.1 script in the Wiki didn't appear to have the correct comments for using Yast's runlevel editor to configure it, I decided to start from scratch and create my own from the skeleton provided with 10.2. I also tested startproc on 10.2 and saw that the permission problem still existed, so I added an "export HOME.." line just before startproc in the script. [Interestingly, my 10.2 script looks a lot like the 9.1 script, except that the 9.1 script will probably fail due to the HOME directory issue, which is easily corrected.] I added a symbolic link from /usr/sbin/rcslimserver to /etc/init.d/slimserver. Once I was satisfied with the script I attempted to start Slimserver. I ran into an error on startup concerning the MySQL message file. Code: -------------------- 070205 21:30:09 [ERROR] Error message file '/usr/local/slimserver/MySQL/errmsg.sys' had only 463 error messages, but it should contain at least 472 error messages. Check that the above file is the right version for this program! -------------------- A quick search turned up a forum entry and a bug report. It seems that for non-i386 systems that Slimserver relies on the local installation of MySQL, but still picks up the included message file, leading to mismatches. This is documented in 'bug report 4615' (http://bugs.slimdevices.com/show_bug.cgi?id=4615). Copying the system message file to the Slimserver MySQL directory fixed the problem. So now Slimserver was able to start, but it wasn't accessible. This is due to the fact that SUSE 10.2's firewall is locked down very tightly. I had to go into Yast and add 9000 (TCP) as well as 3484 (TCP/UDP) to the firewall as allowed ports. Once the firewall was open I could access Slimserver via HTTP and configure it. Since I was now confident that Slimserver would start, I invoked "insserv slimserver" so that the proper rc#.d links would get created (insserv looks at the comments in the init script to determine which runlevels to use, just like Yast's runlevel editor). In terms of performance, it seems to be pretty good. The initial scan took just under 5 minutes to index 517 albums with 6350 songs by 356 artists. The system load average during the scan was between 1.3 and 1.5. After the scan, load average, even while streaming was never above 0.10 and swap shows only 84KB used (with no other active processes, such as Beagled, which is a dog, no pun intended). The system configuration: - AMD Athlon(tm) 64 Processor 3700+ - BIOSTAR GEFORCE 6100-M9 motherboard - 1GB DDR 400 (matched pair of Kingston Value RAM 512MB sticks) (32MB shared for on-board video, though) - Hitachi HDS72168 80GB SATA 3.0Gb/s for / and 2GB swap partition - Maxtor 7H500F0 500GB SATA 3.0Gb/s for /data (where music resides) -- AubreyCTurnerJr ------------------------------------------------------------------------ AubreyCTurnerJr's Profile: http://forums.slimdevices.com/member.php?userid=9795 View this thread: http://forums.slimdevices.com/showthread.php?t=32507 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
