Thread: maemo-optify-boottime.log growing every boot
View Single Post
ikerrg is offline ikerrg
2012-11-08 , 10:32
Posts: 181 | Thanked: 82 times | Joined on Jan 2010
#7
Originally Posted by reinob View Post
Well, I don't (still) know what exactly those packages "optify", i.e. how they decide which file/folder to move away and symlink. It might be useful, but most probably not
You have more info about the set of scripts in http://maemo.gitorious.org/maemo-af/...e/trees/master
The file maemo-optify-auto-opt.conf shows what is checked for optification. Not very useful.

Originally Posted by reinob View Post
From what I've been able to read from the .deb the script will check if the log has reached a certain size, and if so, delete it and start again. Probably this is what happened to you, and you just happened to notice that log file after the first log/previous logs had already been deleted.
OK, I think you got it!!! This must be the reason. So it is a bogus code in the original maemo scripts!!

Originally Posted by reinob View Post
If you find anything interesting, let us (at least me know!
Only one thing about your code. The dfree function outputs the free size (at least it should) in MiB. So you should change your code to:
Code:
dfree()  
 {  
   space=`df -B 1 | tail -1 | awk '{ print int($4/(1024*1024)) }' `  
   [ $? -ne 0 ] && return 0  
   return $space  
 }
Very smart code, indeed!! I will change it in the original script and check what happens.

Regarding your optimizations in your N900, it would be very interesting if your write a guide about which packages, boot scripts and whatever can be removed/commented in order to make N900 faster. It seems very interesting for me!!
Last edited by ikerrg; 2012-11-08 at 10:39.
 

The Following 3 Users Say Thank You to ikerrg For This Useful Post: