similar to: rsync over Iridium modem, 240 bytes per second

Thanks for reply, but this is irrelevant, I'm looking for an *Iridium* gateway. Regards, -- Jean-Denis Girard SysNux Syst?mes Linux en Polyn?sie fran?aise https://www.sysnux.pf/ T?l: +689 40.50.10.40 / GSM: +689 87.797.527 Le 03/04/2018 ? 16:05, albert zhang a ?crit?: > http://www.dinstar.cn/en/index.php/GSM/ > > 2018-04-04 10:01 GMT+08:00 Jean-Denis

Hi list, I have a request to integrate Iridium in a Asterisk system. A quick search didn't return much: I expected to find products similar to GSM gateways, but this does not seem to exist. so I'd be very interested about possible solutions. Has it be done already, how? Thanks, -- Jean-Denis Girard SysNux Syst?mes Linux en Polyn?sie fran?aise

Hello list! I must confess i am kinda new to rails and my experience is truly limited. I am searching to do a *quite* simple thing with rails. I have a db. It has a table with users etc and works fine as it is. I now want to add some very simple authentication mechanism. Instead of authenticating through the use of a rails plugin that handles sessions etc, I want to be able to route the

Hola A todos. Aún no he podido encontrar la causa de porqué la libraría tibbletime, al transformar la tabla a AS_TBL_TIME ME ARROJA EL SIGUIENTE EL SIGUIENTE MENSAJE Error: assert_that: assertion must return a logical value Si alguien ha tenido ese mismo problema, solicito ayuda al foro. El seguimiento de la transformación es el siguiente; library(tibbletime)

Hi Is there a way to estimate the number of bytes per second from the information passed in the th_info-struct to the Theora encoder's th_encode_alloc()? I'm trying to be able to give users a rough estimate of the file size needed to encode with the setting provided to th_info-struct (frame width/height, fps_numerator/fps_denominator, target_bitrate and quality). -- Bjoern

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

Mark II of the patch set. The first patch (dynsumlen2.patch) increments the protocol version to support per-file dynamic block checksum sizes. It is a prerequisite for varsumlen2.patch. varsumlen2.patch implements per-file dynamic block and checksum sizes. The current block size calculation only applies to files between 7MB and 160MB setting the block size to 1/10,0000 of the file length for a

Wayne replied to my original note which said that in a special situation that I was using to probe rsync to build a behavioral model that bwlimit= resulted in bimodal behavior around a 4000 kbyte/sec value. He responded with a patch that I have tested in a limited way. I have a push scenario from a local site to a remote site. I use a file that is 6.3 Megabyte in size whose checksums (when

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

Hi, Is there a way to do rsync with varying bwlimit during the transfer. I tried to look using Linux 'tc' but it looks trivial. Do somebody has working model for it? Our pipe is limited and we don't want to give everything to rsync, We have situation where we want rsync transfers to scale up or down within a specified bandwidth limit. For e.g. if there are two (or multiple) rsyncs

On Thu, 23 May 2019 18:22:03 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > To support protected virtualization cio will need to make sure the > memory used for communication with the hypervisor is DMA memory. > > Let us introduce one global cio, and some tools for pools seated "one global pool for

On Thu, 23 May 2019 18:22:03 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > To support protected virtualization cio will need to make sure the > memory used for communication with the hypervisor is DMA memory. > > Let us introduce one global cio, and some tools for pools seated "one global pool for

On Fri, 10 May 2019 00:11:12 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Thu, 9 May 2019 12:11:06 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Wed, 8 May 2019 23:22:10 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Wed, 8 May 2019 15:18:10 +0200 (CEST) > > > Sebastian Ott <sebott

On Fri, 10 May 2019 00:11:12 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Thu, 9 May 2019 12:11:06 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Wed, 8 May 2019 23:22:10 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Wed, 8 May 2019 15:18:10 +0200 (CEST) > > > Sebastian Ott <sebott

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

Skipped content of type multipart/signed-------------- next part -------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

https://bugzilla.samba.org/show_bug.cgi?id=7349 Summary: Add --limit-time=<seconds> and --fit-time=[seconds] options Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org

My impression when running with --bwlimit in combination with compression -z is that the speed to the filesystem is limited to the value given in --bwlimit. This must be contrary to the intention with --bwlimit. David

Hi, I have two issues with the --bwlimit parameter to rsync which are not mentioned in the FAQ (please correct me if I am wrong): 1. When both an rsync client and an rsync daemon specify the --bwlimit parameter, the client's value overrides the server's value. This could be used in a DOS attack if the client uses a larger value than the server intended. The documentation also is

On Wed, Aug 19, 2020 at 03:07:04PM +0100, Robin Murphy wrote: >> FWIW, I asked back in time what the plan is for non-coherent >> allocations and it seemed like DMA_ATTR_NON_CONSISTENT and >> dma_sync_*() was supposed to be the right thing to go with. [2] The >> same thread also explains why dma_alloc_pages() isn't suitable for the >> users of dma_alloc_attrs() and