|
|
|
|
#1 |
|
Junior Member
Join Date: Jul 2001
Posts: 18
|
how to identify sc-dnas servers on debian
hi,
i'm running 5 sc-dnas servers on one debian machine. all are running in background. now my problem is that i can't identify the streams in order to restart one. the other problem is that sc-dnas starts 2 or 3 processes each server. how can i solve this? i need a simple way to identify which process runs which server. thanks, jaspal |
|
|
|
|
|
#2 |
|
Senior Member
|
The way I solved it for me is I don't make them go into the bg.. I keep them all in fg and use screen.
|
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Jul 2001
Posts: 18
|
can you tell me exactly how you start them. what if i log off that machine? will the processes terminate?
|
|
|
|
|
|
#4 |
|
Moderator
Join Date: Apr 2000
Posts: 4,491
|
Check out the options in the ps command.
Something like: ps -eo "%p %a" might work. At least you should be able to see which .conf is with each sc_serv process using something like that. Tom |
|
|
|
|
|
#5 |
|
Major Dude
|
if you run them, giving a location to a conf file, then the server will be listed in the processes, with the location of the config file
use different config files for each server and wolla, you will be able to identify them by the config file thats associated with them |
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Jul 2001
Posts: 18
|
thanks a lot for your help. the commend is exactly what i was searching for. maybe you can help me with another problem.
when starting a shoutcast server on my debian machine, it creates 6 processes (!). this makes it quiet hard to restart or stop a server. on my redhat&freebsd testing machines each server runs in one process. any idea of how to solve that problem? |
|
|
|
|
|
#7 |
|
Moderator Alumni
Join Date: May 2000
Location: Next Door
Posts: 8,942
|
does it not log the pid to your sc_serv.log file?
-Jay | Radio Toolbox.com |
|
|
|
|
|
#8 |
|
Major Dude
|
yea the pid of the parent process is logged to the logfile
what u need to do, is go to the end of the log, then scrol up until you see a pid, that will be hte pid of the parent process i, personally, thinks the shoutcast server should log the current pid to sc_serv.pid or something |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|