Hi,For applying the change of limit_lifetime, should I add this parameter also at the /usr/share/ibrdtn/build-config.sh as I did with the option limit_payload?So, the queue is big enough to keep all the bundles that we create?Thanks,TheodorosOn Thu, Mar 6, 2014 at 11:46 AM, Johannes Morgenroth <morgenroth@ibr.cs.tu-bs.de> wrote:
Am 06.03.2014 11:31, schrieb Theodoros Bourchas:
> So, with above options, I would expect around 5000 bundles of 100KSound like your bundle lifetime is too short to reach the destination on
> stored in the temporary folder of my device.
> Observing the logs, I could see in the daemon of the sender 4207
> 'TransferCompletedEvent' and 4212 'BundleReceivedEvent' in the daemon of
> the receiver.
> After some time that the experiment was running smoothly,
> 'TransferAbortedEvent' were triggered at the sender and
> 'BundleExpiredEvent's were triggered in the receiver. As a result, the
> already stored bundles in the receiver side started to being deleted.
> Any guess of why there is such a behavior?
time.
Yes.
> The option 'limit_lifetime' is expressed in secs, correct?
This defines the amount of bundles queued at once for transmission. A
> Can you explain what is defined with option bundles_in_transit?
change of that value is not necessary in most of the cases.
Kind regards,
Johannes Morgenroth
--
Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund
Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23
Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig
--
!! 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.