Ditto for me too. Only I'm running on Windows XP (Service Pack 2) and hadn't had enough time to devote to looking at the logs to make me feel justified in complaining. But I did want to at least chime in with another datapoint and if necessary, I can try to carve out some time to run tests as long as the wife is not trying to listen to music at the time.

In my case, I have slimserver running as a service as a particular user so that it can access my large music archive shared from NSLU2 with the index information in Itunes on the PC the server is running on (a dual-Xeon with 2 gigs of RAM). With the latest release, the server would just stop responding at a random time during song playback. The display on the client would be blank and the server would not serve up web pages. I'd have to stop and restart the service to get things going again.

Since I didn't have time to play with it, I rolled back to the 3/26 build which was the build I was using successfully before I upgraded to the release version.

- Paul


Dave Horoschak wrote:
I've been having lockup problems since 6.0b2 and continue to have them with the 6.0 release. On a Mandrake 9.0 dedicated (Samba) file server, I installed SlimServer. Previously, the system had been up & running with a problems for about 2 years. Now that I installed SlimServer, it dsoesn't stay up for more than 24 hours. It locks up hard so that I can't Telnet in, the webserver doesn't work, etc.

What's the best way of troubleshooting this problem? slimserver.log doesn't have any data in it. After a reboot, everything seems to run fine until it crashes again.

Indidentally, this occurs without any Slim clients ever connecting to the server.

Any thoughts?
- Dave

_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to