Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 1504dd8e1c3434d1528527c429500ef8aba6fb44 Author: Marek Lindner mareklindner@neomailbox.ch Date: Fri Jan 30 09:32:37 2009 +0000
doc: batmand/Coredump: update ulimit section as suggested by chris
1504dd8e1c3434d1528527c429500ef8aba6fb44 batmand/Coredump.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/batmand/Coredump.textile b/batmand/Coredump.textile index ca8907d1..ed79a982 100644 --- a/batmand/Coredump.textile +++ b/batmand/Coredump.textile @@ -12,10 +12,10 @@ As coredumps save the programs memory on the hard disk the coredump files [[BR]] can become quite large because some applications consume a lot of memory. [[BR]] On embedded devices (e.g. small routers) a coredump can fill the entire disk [[BR]] - easily. Therefore the tool "ulimit" allows you to control what memory size is too [[BR]] - big to be saved on disk. A "ulimit -c 20000" saves coredumps of up to 20MB, [[BR]] + easily. Therefore the tool "ulimit" allows you to control what memory size is [[BR]] + safe to be saved on disk. A "ulimit -c 20000" saves coredumps of up to 20MB, [[BR]] "ulimit -c unlimited" saves everything no matter how big it is. You can check [[BR]] - your systems default by running "ulimit" without any options. If the value is [[BR]] + your systems default by running "ulimit -c" without any value. If the setting is [[BR]] too small or coredumping is disabled you have to run "ulimit -c <value>" each [[BR]] time before you start batman. [[BR]]