[Solved] Reduce boottime

[Paul_123]

I’m not sure you have shown us your onboot.lst. 40 extensions seems like a lot for WiFi ssh and sound.

[michnixweiss]

onboot.lst attached

[Paul_123]

So you have extra extensions loaded that are only needed for development.
 
i2c-tools
p_ython3.8-pip
nano

Not sure what is in your startUp extension

The tcz startup scripts taking 10seconds to run seems quite long.

[michnixweiss]

Hi @Paul_123,

I switched i2c-tools to ondemand, without change. I temporarely removed all python from the onboot.lst but I'm still at

Code: [Select]

cat /tmp/bootlog.txt
   0.0 - Build TCZ list
   2.3 - Mount TCZ (35)
   2.6 - Add to file system
  10.2 - Execute startup scripts
   0.1 - udev trigger
My startUp extension is/was a test for the easiest way to autostart things. I want to save me the need for an entry in bootlocal.sh
I think using the tce.installed folder will be the easier way...
But for boottime it doesn't matter from where things are startet.

So onboot.lst is now

Code: [Select]

firmware-rpi-wifi.tcz
wifi.tcz
openssh.tcz
nano.tcz
onoffshim-1.2.tcz
wm8960min_5.10.77-piCore.tcz
alsa.tcz
alsa-utils.tcz
alsa-plugins.tcz
rng-tools.tcz

bootsync.sh (without comments) is not changed

Code: [Select]

/usr/bin/sethostname box
/opt/bootlocal.sh &

bootlocal.sh is this

Code: [Select]

cannot post this - attached file


[Paul_123]

The problem is that using a tce.installed script is a blocking activity.  It is best to put your startup activities in bootlocal.sh.  And run them in the background if possible.

[michnixweiss]

The problem is that using a tce.installed script is a blocking activity.  It is best to put your startup activities in bootlocal.sh.  And run them in the background if possible.

Ok, get it.

How can I figure out what is causing the 10sec?

[Paul_123]

If I have to guess, it’s ca-certificates.   Look in /usr/local/tce.installed. The scripts are there,  if there is no script, tce-load just creates a zero length file so the system knows it’s loaded.

[michnixweiss]

/usr/local/tce.installed/ca-certificates

Code: [Select]

cannot post the script, file attached
But what shall I do with it to fasten it up? ca-cerfificates extension is required by openssh, python, wifi, etc
I could include the files to the filetool.lst and remove the script from the extension if that helps!?
Otherwise there are only scripts from wifi and file. The rest in tce.installed are zerofiles.

[Paul_123]

Not much.

[Rich]

Hi michnixweiss
Try this:
Remove the startup script from  ca-certificates.tcz  and save it to  /opt.
Then make sure it's executable:

Code: [Select]

sudo chmod 775 /opt/ca-certificates
Place the following in  bootlocal.sh:

Code: [Select]

cp -f /opt/ca-certificates /usr/local/tce.installed
/usr/local/tce.installed/ca-certificates &

[michnixweiss]

First of all many thanks! Now I'm at

Code: [Select]

cat /tmp/bootlog.txt
   0.0 - Build TCZ list
   2.3 - Mount TCZ (34)
   2.5 - Add to file system
   3.8 - Execute startup scripts
   0.1 - udev trigger
And ssh is reachable after about 28sec.

One question to the "trick": why copy ca-certification back to tce.installed before run it?

Is there anything else I can optimize to reduce boot time?

[michnixweiss]

I decided to make a bootlocal dir for extensions
As an example the ca-certification.tcz:

Code: [Select]

- in squashfs-root -
mv usr/local/tce.installed/ca-certificates usr/local/tce.installed/ca-certificates.sh
mv usr/local/tce.installed usr/local/bootlocal
Then added to my /opt/bootlocal.sh

Code: [Select]

cannot post - attached fileDoes the job, I can use it for my own extensions and have a small log for them 

[Rich]

Hi michnixweiss

... One question to the "trick": why copy ca-certification back to tce.installed before run it? ...

Simple, I didn't think that one through. You could just execute it from  /opt/.

[michnixweiss]

So if there is no more possiblity to reduce boot time this can be set to solved.

Thanks @Rich and @Paul_123

[Rich]

Hi michnixweiss
Then solved it is.