search for: msg00153

...wd during startup, which now fails if the current directory is unreachable. Further references: https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html https://bugzilla.redhat.com/show_bug.cgi?id=1542180 Andreas Schwab agrees that rsync is buggy: https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html Thanks, Florian

...rent directory is > unreachable. > > Further references: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html > https://bugzilla.redhat.com/show_bug.cgi?id=1542180 > > Andreas Schwab agrees that rsync is buggy: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html > > > Thanks, > Florian > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users > -- Thanks and Regards, Kotresh H R -------------- next part ---------...

...is unreachable. Further references: https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html[https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html] https://bugzilla.redhat.com/show_bug.cgi?id=1542180 Andreas Schwab agrees that rsync is buggy: https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html[https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html] Thanks, Florian _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org[mailto:Gluster-users at gluster.org] http://lists.gluster.org/mailman/listinfo/gluster-users -- Thanks and Reg...

Since 1.4.22 realtime status for sip peers seems to be broken. If I do a "sip show peers" from the CLI I get this: 2001/2001 192.168.2.234 D 5060 UNKNOWN Cached RT It is arbitrary which peers will say OK and which will say UNKNOWN and it changes over time. This is a problem with an application like the Asternic Flash panel because it uses the peer

(resending, sorry for duplicates) On 01/24/2018 05:59 PM, Dietmar Putz wrote: > strace rsync : > > 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 getdents(3, /* 0

This rounds up the remaining bugs that I originally identified in: https://www.redhat.com/archives/libguestfs/2020-July/msg00153.html Eric Blake (4): api: Permit export list APIs when Connected info: Support --list with serializing servers info: Fix --json output when list size != 1 info: Permit --size --json generator/API.ml | 6 +++--- info/info-list-json.sh | 9 +++++++++ info/info-list.sh | 9 +++...

Hi all, i have made some tests on the latest Ubuntu 16.04.3 server image. Upgrades were disabled... the configuration was always the same...a distributed replicated volume on 4 VM's with geo-replication to a dist. repl .volume on 4 VM's. i started with 3.7.20, upgrade to 3.8.15, to 3.10.9 to 3.12.5. After each upgrade i have tested the geo-replication which worked well anytime. then i

v1: https://www.redhat.com/archives/libguestfs/2019-November/msg00153.html v2: - Fix implementation of can_cache. - Add implementation of can_fua. - Add a very thorough test suite which tests every command + flag combination.