aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/respawn.sh
AgeCommit message (Collapse)AuthorFilesLines
2013-03-16sysmobts: Name the screen and use '-X quit' to shut it downHolger Hans Peter Freyther1-0/+2
Use "kill -2 0" for the PCU as SIGTERM is not handled yet. With the current set of code the stop function will stop both the PCU and the BTS.
2013-03-16respawn: Adjust the oom score for the supervisor and bts/pcu, increase sleepHolger Hans Peter Freyther1-1/+11
Make the script mostly unkillable due to OOM and make sure that the process has a score of zero. Wait 10 seconds before re-launching. The combination of ( && exec ) & appears to save one sub-process. The script has been tested with bash and busybox's ash.
2012-06-15respawn: The BTS should not be nice, make sure the BTS is the most favorableHolger Hans Peter Freyther1-1/+1
2012-06-01sysmobts: set the RF ACTIVE LED when we bring RF upHarald Welte1-0/+1
Once we get RF-ACTIVATE.conf from L1, we now enable the corresponding LED. We also switch it off on RF-DEACTIVATE.conf. We do _not_ switch it off when osmo-bts crashes or terminates before RF-DEACTIVATE.conf. The latter is intentional, as RF may very well still be active at that point. The re-spawning script will re-set the DSP and therby turn off the RF and then disable the LED. A better solution might be to do all this in the kernel driver for the DSP.
2012-05-14contrib: Re-load the firmware before restarting the main applicationHolger Hans Peter Freyther1-0/+1
More recent firmware appears to have issues even after a clean shutdown, make sure to fully reset the DSP before starting the BTS software.
2011-07-01add respawn script and screenrc for respawning the process in screenHarald Welte1-0/+4