|
|
#1 |
|
Major Dude
|
My Question or problem is I can easly host a station off my DSL on my Windows computer but when I try to host it off my Webhost's Red Hat Linux server it disconnects after a couple a minutes from the telnet host and my broadcast goes down although it does work for a few minutes. I tried the background thing and it didn't work. Maybe it is cause I did it wrong I don't know. Any help would be great.
|
|
|
|
|
|
#2 |
|
Senior Member
Join Date: Nov 2000
Posts: 176
|
Maybe your provider doesn't allow that process and is killing it...
|
|
|
|
|
|
#3 |
|
Major Dude
|
I thought the same but I checked there policy and agreement and it mentions nothing about mp3 streaming or mp3s just no porn. So I don't think it is that. Usually you get timed out from Telnet no matter what so I am trying to find out why it won't stay running in the BG.
|
|
|
|
|
|
#4 |
|
Member
Join Date: Jan 2001
Posts: 68
|
You need to find out what their policy on background processes is. I had an ISP that just plain out didn't allow them, and had an automation killing them off when it found them.
Try running the process in a shell script loop (in the foreground), capture the exit status code (if any), and see if it's failing or being killed from the outside. Ruph |
|
|
|
|
|
#5 |
|
Major Dude
|
I understood the part about not allowing background processes but I don't understand the forground looping with scripts. Could you clarify or help me do that.
|
|
|
|
|
|
#6 |
|
Member
Join Date: Jan 2001
Posts: 68
|
This is a little hard to explain without knowing what shell(s) you're comfortable with. The example below should work under BASH or SH.
#!/bin/bash X=0 LOGFILE="/tmp/dnas.log" while [ ${X} = 0 ] do <shoutcast DNAS command line here> echo "DNAS Exit Code: $? at `date`" >> ${LOGFILE} done This will endlessly loop restarting the DNAS server each time it exits. The $? above is an internal variable in the shell which holds the exit status of the last command that exits. You should probably read up on the various Unix shells. At a prompt, try entering man bash or man sh. Also, there's a decent tutorial on BASH at http://www.fsf.org. Ruph |
|
|
|
|
|
#7 |
|
Major Dude
|
Thanks I will try that if I need to but I have a new host and I think the owner can help me since it is his computer.
|
|
|
|
|
|
#8 |
|
Member
Join Date: Oct 2000
Posts: 81
|
You might try 'nohup'ing' the process-
run that above script like this: nohup script name that keeps the OS from killing the process when you logout or disconnect (HUP = Hang Up). |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|