search for: ransferred

Displaying 6 results from an estimated 6 matches for "ransferred".

Did you mean: transferred
2005 Sep 26
1
sip, call ransfer and call waiting
Hello all, I have a very basic question but I haven't found any answer. I would like to configure asterisk so that it wil not indicate a call waiting to a SIP phone if it is already on conversation (off hook). But I don't want to loose call transfer, call hold and so on. Is there any possibility to do that? Regards, Daniel ANDRE -- Daniel ANDRE (mailto:daniel.andre@iris-tech.fr)
2009 Jun 03
3
remove-source-files checking for open files?
hi We have a box here connected to an antenna receiving rather large amounts of metheorological data from a satellite. the data is received and ransferred to another box and removed from the receiving server. I first thought of using rsync for this, but it seems --remove-source- files has no way of checking if the file is open or not, so if the receiving process is still writing to a file, rsync will transfer the file and unlink() it without b...
2020 Aug 07
3
Rsync 3.2.3 released
I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz.asc See the
2020 Aug 07
3
Rsync 3.2.3 released
I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz.asc See the
2020 Aug 07
0
Rsync 3.2.3 released
Rsync 3.2.2 ransfer rate on my pet hardware is really poor, so every improvement counts. I noted that rsync writes a gmon file on the source path and leaves it there when it terminates. When the source path is read-only, rsync complains that it cannot write in it. For optimal use of the input bus, no write commands should be used there. Can you look into it? Also, I have 12GB of cache in ecc ram
2020 Aug 07
1
Rsync 3.2.3 released
Hi Wayne, I see that a couple of patches from the rsync-patches tar have disappeared, like acls.diff or xattrs.diff yet I don't see the changes in the code. Is there a reason for their removal? Were they applied differently on the code and are no longer needed? Thanks for any info on this. Regards, Michal Ruprich On 8/7/20 7:45 AM, Rupert Gallagher via rsync wrote: > Rsync 3.2.2