September 20, 201015 yr Not much of a script but I find it helpful for me to start up sickbeard if I have had to shut it down. Only problem is it causes unMenu to crash. Could someone tell me how to correct this? #define USER_SCRIPT_LABEL Start SickBeard #define USER_SCRIPT_DESCR Start SickBeard #UNMENU_RELEASE $Revision: 7 $ $Date: 2010-03-29 23:12:23 -0400 (Mon, 29 Mar 2010) $ nohup python /mnt/cache/_custom/usr/share/packages/sickbeard/SickBeard.py & Oddly this script works fine, though if it needs something else to make it more clean then I would like to know. #define USER_SCRIPT_LABEL Start SABnzbd #define USER_SCRIPT_DESCR Start SABnzbd #UNMENU_RELEASE $Revision: 7 $ $Date: 2010-03-29 23:12:23 -0400 (Mon, 29 Mar 2010) $ #Find local IP and start SABnzbd on it IP=`ifconfig eth0 | grep 'inet addr:'| grep -v '127.0.0.1' | cut -d: -f2 | awk '{ print $1}'` python /mnt/cache/_custom/usr/share/packages/sabnzbd/SABnzbd.py -d -s $IP:88 Thanks
September 20, 201015 yr Maybe it's something about the nohup command and the feedback of the job n° and process ID that causes unMenu to crash.
September 22, 201015 yr Author well tried with nohup removed and unmenu still crashed. Not sure what to do with the job n° and process ID. Its the same line of code I use in my go script and I don't have any problems there. Just something to do with unmenu.
September 22, 201015 yr well tried with nohup removed and unmenu still crashed. Not sure what to do with the job n° and process ID. Its the same line of code I use in my go script and I don't have any problems there. Just something to do with unmenu. how does it "crash" ?? Does it just not return? It may be that you cannot put tasks in the background in a user-script with an "&" I never tried. It is more likely that unMENU is waiting for all the output from the process, and you did not re-direct it, so it waits forever. Try something like this instead: echo "python /mnt/cache/_custom/usr/share/packages/sickbeard/SickBeard.py" | at now + 10 seconds That way the "at" command will start the process, and it will disassociate itself from the unMENU process. If you wish, you can also try nohup python /mnt/cache/_custom/usr/share/packages/sickbeard/SickBeard.py >/tmp/sickbeard.out 2>&1 & At least that way, the output is not keeping unMENU from returning.
Archived
This topic is now archived and is closed to further replies.