Hi jazzbiker,
No, restore is called just right before bootsync.sh. Unless some races, $HOME must have existed.
Sounds right. I put the code in different places now (like /mnt/mmcblk0p2/app ... - makes that one even sense?) and nothing changed. Also the full path to python3.6 changed nothing.
I also took a second pi ("normal" 1.2 B+) with a new sd card, picore 9.0 and an ethernet connection for sanity checking. Still got the same issue.
But then i wrote a absolute minimal test script without any pip (!) module imports. It's just a print every second in an endless loop. And that one works. At least i see the python process running in top. The modules are persistent (tested with manual execution after reboot). But is it possible, that the modules / the folder are / is not there yet during the execution of the bootlocal script?
I followed that answer for pip installation: newbielink:https://unix.stackexchange.com/questions/569703/does-tinycores-picores-python-limits-prevent-python-library-installation-for
[nonactive]The modules are in ~/.local/lib/python3.6/site-packages/
Not in usr/local/lib/python3.6/site-packages/
EDIT: Yes, just double checkt it. The scripts are not executed during boot as soon as I import a module which was installed via pip.
Strange, that the log file is empty. I imagined that i would see errors (like import errors) there. Thats the reason why i not looked into this earlier.