View Single Post
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#55
Originally Posted by kaze.daniel View Post
what about that:

HTML Code:
# my rcS.e fix

start on started rcS-late

script
       echo 30 > /proc/sys/vm/swappiness
       echo 0 > /proc/sys/vm/page-cluster
       echo 1 > /proc/sys/vm/laptop_mode
       echo 1 > /proc/sys/vm/oom_kill_allocating_task
       echo 0 > /proc/sys/vm/dirty_expire_centisecs
       echo 0 > /proc/sys/vm/dirty_writeback_centisecs
       echo 60 > /proc/sys/vm/dirty_background_ratio
       echo 95 > /proc/sys/vm/dirty_ratio
       echo 0 > /proc/sys/net/ipv4/tcp_timestamps
       echo 1 > /proc/sys/net/ipv4/tcp_no_metrics_save
end script
Just add first 4 lines to be in sync with coding standards:

Code:
description "it is my own N900 tuning"
author "YourName"

console output
instead of ugly line started from # (sorry for that). And please - enclose any numeric value before '>' sign into double-quotes like

echo "95" > /proc/sys/vm/dirty_ratio

It could not expose you to very common bug - the sequence like '95>' without space has a special meaning in shell.

Note: I didn't evaluate the effect of that "echo" commands.
 

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