Python-Script for Autostart, what is the best way?

Hi,

I've got a running Python-Script for recording VoIP-Calls from my Fritzbox (legal-issues etc are clear; those who call on that special number know about the recording).

As my Computer (currently running the script) is not on "always on" anymore, I wanted to move that script over to my OMV-Installation.

As I have to "operate on the open heart", I'd like to ask experienced user on how to get the script running (without ruining the current installation)...

Plan:
python-script starts automaticly.

Problem:
I'd like to avoid any init.d-solutions as these might be overwritten by an upgrade/update/systemchange.
...what is the best solution to get the script running by startup?

(sorry for asking so "thumb", I'm quiet absorbed by the reason why I have to record the calls)

Thanks for your help!

A few years ago, I lost "custom init.d"-Start-Scripts after an update...
Don't want to take Chances (especially if there are "nicer" ways to do it)...

@emsic

...only if you're using a Fritz!Fon-Device, and then only for 10 Minutes...
Unfortunatly, the current messed up Situation requires longer calls...

But if you have a way to let "fritzcap" running directly on the Fritzbox?

@all

Ok, thanks - I'll try to get it running with init...
But it will have to wait for weekend...

Hi again,

Have to bring that topic up again, as I encountered an annoying issue:
I created an Init.d-Script for the capture-script, the script starts - but can't connect to the fritzbox WHEN started at bootup... If I log in to ssh, and start the init.d-script by myself, everything is working fine.

The script:

#! /bin/sh
### BEGIN INIT INFO
# Provides:          thescript.py
# Required-Start:   $network $remote_fs $syslog $local_fs 
# Required-Stop:     
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: thescript
# Description: thescript
### END INIT INFO


# Variablen
box_name= <<fritzes IP>>
passwd= <<the password>>


# Funktionen
do_kill() {
    ps -ef | grep " thescript.py " | awk '{print $2}' | xargs sudo kill
}
do_start() {
    /usr/bin/python /the/path/to/thescript.py --box_name $box_name -p $passwd -c -m -d &
}


# Aktionen
case "$1" in
    start)
        echo -n "Starte thescript..."
    if [ `pgrep thescript.py|wc -l` = "0" ]; then do_start
        echo "OK"
    else
        echo "FAIL"
    fi
        ;;
    stop)
        do_kill
        ;;
    restart)
    do_kill && do_start
        ;;
    status)
    ps -e | egrep thescript.py
    ;;
esac


exit 0

Adding some test-parts to the init-script (a simple ip addr-string to show current IP-Adress) I found out, that during bootup, the init-script seems to be unable to use the network, eventhough I got is as depency... The script does get started, but the own log of the script shows just "cannot connect to fritzbox"...

I'm running 2.1.18 - is it possible that it is using system.d already?
Does anybody see the error in my script?
(kinda annoying to have to log in to ssh and start the script by myself after a reboot)

Yes, $all doesn't change anything...

System's on staticDHCP...

Setting to manual IP:
worth a try, BUT:
checking the issue, I also had a "wait with this script until an IP-Adress has been taken"-Brake in the script, didn't work either...

Using with Scheduled Task, sorry, forgot to mention it: tryed that also, having the same issue...

I'll give the manual IP-thing a try now... (hate to play around there on a headless-system

Manual-IP didn't work either, but stumbling over "if-up.d" while changing IP-Settings, I gave that a try...

I created a bash-script to call the python-script (yes I'm kinda old school - could have called it directly), placed it in /etc/network/if-up.d , added executable-bit, (removed everything that-script-related from init.d) and rebooted...

Seems to be working... Have to test it a few days (including rebooting)