Thread: maemo-optify-boottime.log growing every boot
View Single Post
reinob is offline reinob
2012-11-08 , 09:40
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#4
Originally Posted by ikerrg View Post
@reinob

The file /var/log/maemo-optify-boottime.log is coming from the package maemo-optify-runonce. Why you don't have it installed? It is odd, I have not changed any official package in my device and it is reflashed one month ago with the latest rootfs and eMMC images.
Well, I guess the "runonce" made me decide to uninstall it. If it was (pre-)installed and did its thing already ("once"), then why should it continue to be installed polluting my dpkg database

In addition, I do not understand why since the last week a process is executing this file on boot. How can I find where it is called on booting?
AFAIK in /etc/event.d/rcS-late (where /home is mounted) and (where one of the possibilities for *generating a reboot loop* is present -- "if fail to mount /home and system already optified")

When /home is mounted OK and not in ACT_DEAD mode /usr/sbin/maemo-optify-firstboot.sh is called.

Then /opt is mounted, and then /usr/sbin/maemo-optify-auto-opt.sh is called (if it exists).

So I guess the script (if it exists) runs at *every* boot, makes a messy calculation of a bogus number and logs it in a file taking space in rootfs (not much, but hey..)

I'd suggest you just uninstall every package containing the string "optify" *except* pymaemo-optify. That's a whole different beast, and I still have to find a nice way of having optified-python without all that bind-mounting party.
 

The Following 2 Users Say Thank You to reinob For This Useful Post: