Jack Coates wrote:
Either slimserver is already running, or something else is using its network port. As root, ps aux | grep slimserver.
That won't show if another process is listening to that port.
If you have the "lsof" (list open files) command, that's a better way to get the information you need. E.g., if I do
sudo lsof | grep TCP
on the Linux machine that runs my slimserver, I'll get (heavily edited):
slimserve 32635 slimserver 8u IPv4 5470505 TCP *:3483 (LISTEN)
slimserve 32635 slimserver 9u IPv4 5470506 TCP *:9000 (LISTEN)
slimserve 32635 slimserver 10u IPv4 5470507 TCP *:9090 (LISTEN)
slimserve 32635 slimserver 11u IPv4 5709439 TCP homer.local.ka9q.net:3483->192.168.1.31:35348 (ESTABLISHED)
slimserve 32635 slimserver 12u IPv4 5709440 TCP homer.local.ka9q.net:3483->otto.local.ka9q.net:33030 (ESTABLISHED)
slimserve 32635 slimserver 13u IPv4 5520472 TCP homer.local.ka9q.net:9000->milhouse.wi.local.ka9q.net:51407 (ESTABLISHED)
slimserve 32635 slimserver 32u IPv4 5718345 TCP homer.local.ka9q.net:9000->otto.local.ka9q.net:33036 (ESTABLISHED)
This shows that process ID 32635, named slimserve(r), is listening on TCP ports 3483, 9000 and 9090. Chances are you'll find some old slimserver process still bound to one of the needed ports, and that's keeping you from starting a new one. Kill the old ones and try again.
--Phil _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
