Thanks Johannes.
Before your answer, I had seen using "htop" command that during the execution of dtninbox the memory usage was increasing and when it reached the 28MB (RAM of TP-LINK 3040), the process of dtninbox was killed or even the device was rebooting. So, I made a swap partition to the device with 2GB additional space and after that dtninbox was working. Of course, you solution with dtntrigger is better and faster and it doesn't require any new partition.
Thanks again!
Best, Theodoros
On Tue, Jun 3, 2014 at 3:57 PM, Johannes Morgenroth < morgenroth@ibr.cs.tu-bs.de> wrote:
Hello Theodoros,
thank you for this report. You have unveiled a memory leak in the recent version of dtninbox. By now you can not fix it using the releases, but I can suggest a work-around. The dtninbox mechanism is quite simple, you can replace it by using dtntrigger and a simple script.
Create a new file named inbox.sh with this content...
--- inbox.sh script --- #!/bin/sh #
tar xvf $2 --- end of script ---
Then start dtntrigger like this... $ dtntrigger -w /data/tmp inbox /bin/sh inbox.sh
The script will handle incoming bundles as dtninbox would do.
I made already a patch to solve the mem-leak issue of dtninbox and it is queued for the next release 0.12.2.
Kind regards, Johannes
Am 30.05.2014 17:10, schrieb Theodoros Bourchas:
I can see the entire bundle received correctly under /overlay/TMP/bundles, but when I run the above command, after some time a message "Killed" is appeared. As a result, part of the whole bundle is received (around 10-11 MB), while under /overlay/inboxFolder I can see a blob with the entire size of 100MB.
I would be grateful if you had any hint about this behavior and how I can fix it. Thanks in advance,
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.