Displaying 20 results from an estimated 5000 matches similar to: "DO NOT REPLY [Bug 6067] New: IPv6 literal addresses broken"
2009 Jul 29
2
DO NOT REPLY [Bug 6588] New: errors missed when connecting to host with multiple addresses and host is down
https://bugzilla.samba.org/show_bug.cgi?id=6588
Summary: errors missed when connecting to host with multiple
addresses and host is down
Product: rsync
Version: 3.0.6
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned at
2006 Jan 23
1
[Bug 1675] New: rsync cannot cope with literal IPv6 addresses
Dear Sir or Madam,
Currently, we are using Rsync 2.6.6. I wonder if this version is compatible
with IPv6? I would really appreciate your feedback.
Sincerely,
Nurten Helvaci
-------------- next part --------------
HTML attachment scrubbed and removed
2007 Feb 05
4
DO NOT REPLY [Bug 1675] rsync cannot cope with literal IPv6 addresses
https://bugzilla.samba.org/show_bug.cgi?id=1675
luke-jr+sambabugs@utopios.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luke-
| |jr+sambabugs@utopios.org
------- Comment #2 from
2003 Nov 13
2
IPv6 literal addresses on command line
Hello all,
Can anyone give me a hint on how to specify an IPv6 address in an
rsync address literal - the colon character is already used to
seperate the host name from the remote directory AFAICT... I get, e.g.
rsync -Cavb 3ffe:502:420:120::2:/home/cam/dev/proj
3ffe: Unknown host
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code
2006 Aug 13
5
DO NOT REPLY [Bug 4016] New: literal IPv6 addresses not supported in ssh protocol
https://bugzilla.samba.org/show_bug.cgi?id=4016
Summary: literal IPv6 addresses not supported in ssh protocol
Product: rsync
Version: 2.6.9
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: david.madore@ens.fr
2006 Jul 03
13
Remote Postgres is driving me crazy!
Hi guys,
I need your help. Here is my database.yml:
development:
adapter: postgresql
database: db
username: username
password: mypassword
# Connect on a TCP socket. Omitted by default since the client uses a
# domain socket that doesn''t need configuration. Windows does not
have
# domain sockets, so uncomment these lines.
host: 192.168.22.1 (this is a remote ip in
2003 Jun 18
1
[Bug 598] case sensitive in host matching
http://bugzilla.mindrot.org/show_bug.cgi?id=598
Summary: case sensitive in host matching
Product: Portable OpenSSH
Version: -current
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-bugs at mindrot.org
ReportedBy: misiek at
2009 Mar 08
5
DO NOT REPLY [Bug 6175] New: write last transfer status when timeout or other error happens
https://bugzilla.samba.org/show_bug.cgi?id=6175
Summary: write last transfer status when timeout or other error
happens
Product: rsync
Version: 3.0.5
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2007 Dec 19
1
[Puppet-dev] 0.23.3 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all
There is some discussion of doing a 0.23.3 release to backport a number
of bugs fixes from 0.24.0.
What do people think of this idea? Would you prefer a dot upgrade to
0.23.3 or are most planning to upgrade cleanly to 0.24.x?
I understand from Luke that 0.24.1 will be released shortly and that
0.23.2 clients should cleanly connect and
2010 Mar 09
2
2.0beta3 10876:370ee9717a6c broke listen on literal IPv6 address
Hi,
apparently the following change in dovecot hg
* New revision (10876:370ee9717a6c) in dovecot Mercurial repository:
- config: Forgot to add header file.
broke
listen = 83.170.6.69, 2001:1b10:1000::110:1:1
mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29:
listen=..:port has been replaced by service {
2018 Mar 01
1
Opus implementation on Nordic chip
Hi
I’m currently trying to implement the Opus codec on a nRF 52 DK (from Nordic). One main goal of my project is a low power application that can record and send audio data (16+ kHz) over BLE. Therefore, the Opus audio codec would be suitable to encode audio data, send it over BLE and decode it on another chip.
Unfortunately, I have some trouble implementing it.
There are different parts to the
2014 Feb 08
0
[PATCH v2] arm: Use the UAL syntax for instructions
This is required in order to build using the built-in assembler
in clang.
---
I squashed the two changes since it would break the normal gcc
build otherwise.
---
celt/arm/arm2gnu.pl | 2 ++
celt/arm/celt_pitch_xcorr_arm.s | 18 +++++++++---------
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/celt/arm/arm2gnu.pl b/celt/arm/arm2gnu.pl
index eab42ef..5c24758 100755
---
2014 Sep 16
0
[Bug 1789] On linux use abstract socket for X11 connections if possible
https://bugzilla.mindrot.org/show_bug.cgi?id=1789
Arkadiusz Mi?kiewicz <arekm at maven.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|5.5p1 |6.6p1
CC| |arekm at maven.pl
--- Comment #10 from Arkadiusz
2018 Nov 13
1
dovecot lmtp thinks that "disk quota exceeded" is "internal error"
> On 13 November 2018 at 22:06 Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote:
>
>
> On 13/11/2018 15:54, Arkadiusz Mi?kiewicz wrote:
> >
> > 2.2.36 (not migrated to 2.3 yet) reports such problem:
> >
> >> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703)
2005 Sep 09
1
rsync - No such file or directory
Hi All,
I'm getting the following error and don't know how to fix. Paths are
correct.
I run the rsync and get error and the cursor just hangs.
bash-2.03$ rsync -e ssh -av /export/home/db2inst1/db2_backup
db2inst1@enolagay: /export/home/db2inst1/db2_backup
building file list ... rsync: link_stat
"/export/home/db2inst1/db2inst1@enolagay:" failed: No such file or
2018 Nov 13
0
dovecot 2.2/openssl 1.0 vs dovecot 2.3/openssl 1.1.1 ssl regression
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 13 November 2018 at 20:53 Arkadiusz Miśkiewicz <
<a href="mailto:arekm@maven.pl">arekm@maven.pl</a>> wrote:
</div>
<div>
2016 Nov 21
1
nologin + reason -> logging reason
On Monday 21 of November 2016, @lbutlr wrote:
> On Nov 21, 2016, at 7:39 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote:
> > reason is the only thing in maillog that allows to distinguish why user
> > was not allowed to log in.
>
> Um? the only thing? How about where you set the reason in the first place?
That "first" place is constantly changing
2019 Mar 27
2
Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)
Hello.
I have one account with heavy traffic (big mails) and quite often
indexes get corrupted.
This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28.
When corruption happens lmtp and pop3 segfault on accessing it like:
> Mar 27 11:13:50 mbox dovecot[22370]: lmtp(24428): Connect from local
2014 Feb 07
3
[PATCH 1/2] arm: Use the UAL syntax for ldr<cc>h instructions
This is required in order to build using the built-in assembler
in clang.
---
celt/arm/celt_pitch_xcorr_arm.s | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/celt/arm/celt_pitch_xcorr_arm.s b/celt/arm/celt_pitch_xcorr_arm.s
index 09917b1..3c4b950 100644
--- a/celt/arm/celt_pitch_xcorr_arm.s
+++ b/celt/arm/celt_pitch_xcorr_arm.s
@@ -309,7 +309,7 @@
2009 Jul 17
2
[LLVMdev] regression: double spaced asm output for thumb-2
Something has changed in the last few days that breaks thumb-2 (and
possibly all ARM) assembly output. Some, but not all lines are double-
spaced, for example:
fstd d13, [sp, #+40]
fstd d12, [sp, #+32]
fstd d11, [sp, #+24]
fstd d10, [sp, #+16]
fstd d9, [sp, #+8]
fstd d8, [sp]
sub sp, sp, #872
mov r4, r1
mov r5, r0
cmp r0, #2
ble LBB1_133 @ entry.bb2.i_crit_edge
LBB1_1: @