init.d

[barrybinnenweg]

I’m trying to startup a script at boot by placing it in /etc/init.d
while true; do
python3 p1.py -c 1 -l 10 -pvo Y -pvoapi -pvosys
echo "P1 monitoring script disrupted ... Restarting script."
done

and next: sudo update-rc.d p1script defaults

but this produces a looping script at startup and makes the RPI unresponsive.
What should I change to make this work?

Barry Binnenweg

[Aydan]

Hi Barry

You should not put your looping script into init.d.
Your script in init.d should start your actual script like so:
/your/script/location/script.sh &

this means "start the script but don't wait for it to finish"

Regards
Aydan

[gkreidl]

Have a look at other scripts in /etc/init.d to learn how to create such a script. You'll also find help on the internet.

[DougieLawson]

Sorry Aydan, but you're wrong.

The /etc/init.d scripts normally use start-stop-daemon to get the application daemon started. If you have a badly behaved daemon program that doesn't fork itself into the background you can use start-stop-daemon --background ... to overcome that problem.

There's a skeleton script /etc/init.d/skeleton that gives you the basics of getting a daemon running.

[Aydan]

Sorry Aydan, but you're wrong.

The /etc/init.d scripts normally use start-stop-daemon to get the application daemon started. If you have a badly behaved daemon program that doesn't fork itself into the background you can use start-stop-daemon --background ... to overcome that problem.

There's a skeleton script /etc/init.d/skeleton that gives you the basics of getting a daemon running.

My solution might be wrong, but the reason for it being stuck is still valid.
Whenever you call something from init.d that runs infinitely, the init sequence is stuck.