I am developing new services based on QuecOpen. In general, these services will be called on bootup the system. However, it’s not called after trying many way and many different Start, stop levels.
More details for my way:
Add file to /etc/init.d/hello.init that calls a simple script (already in mod 755)
/etc/init.d/hello.init start
/etc/init.d/hello.init enable
reboot the system
After rebooting, check the status or the output of the script, I can confirm that it’s not started any time yet.
I can see other services introduced by Quectel are starting in the logs below
[ 66.951615] /etc/init.d/start_quectel_slic_daemon start
...
[ 89.771328] Try to start wlan_services based on procd
[ 90.501159] qmi_shutdown_modem service start
[ 95.740843] process_accept_req: 30 callbacks suppressed
So, for developing a new service with QuecOpen is there any special step to add these new services into the bootup process?
Hi,meqqn
can you tell me the model of the module you are currently using?
If you want to add some services to make it call when the system starts.
Try the following steps
Add a file to /etc/init.d/
Create a soft link to the file you added in /etc/rcX.d/(usually rc5.d), it is best to use an absolute path here (otherwise it may not work).
3.sync and reboot
The module we are using is RG255C_Series_5G coming alone with sdx35 code.
I have made similar changes as your suggestion before but not work, the folder is /etc/rc.d instead of /etc/rcX.d as yours. I have 5 new services and they are having the same problem as this.
The symbol links will be created when we call /etc/init.d/<servicename> enable