Hi Jeff,
For the stop levels i.e. 0, 1 and 6 the priority of the custom app is at 1 on my conduit, so its going to be run/shutdown after the lora-network-service and mosquitto has already been shut down.
For the Start level i.e. 2, 3, 4, 5, the Lora-network-service is running at a priority of 80 and the mosquitto is at 75 and the customapp on my conduit is at 95. So I would like to run the customapp between the priority levels of the mosquitto and lora-network-server, say 77. so I would end up running the command as you have mentioned above and as shown below.
update-rc.d customapp defaults 77 1
So once the firmware upgrade has completed I am guessing it will begin any customapp installs. In the post install step, i will remove the customapp init.d settings using the “update-rd.d -f customapp remove” command and install the customapp init.d settings with the changed priority level as shown above. Do you see any issues with this approach or any obvious concerns?
I did make those changes on my conduit to test it out, and this time the custom app starts 20 seconds ahead of the lora-network-server” service and at least i can be assured no loss of packets, because of service startup delays.
Thanks,
Ajay.