similar to: [Bug 8456] New: improve --link-dest bahaviour

https://bugzilla.samba.org/show_bug.cgi?id=8450 Summary: --link-dest seems not to work mounted NTFS file systems Product: rsync Version: 3.0.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.mindrot.org/show_bug.cgi?id=2269 Bug ID: 2269 Summary: ssh-copy-id: does not respect .ssh/config Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-copy-id Assignee: unassigned-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=3722 Bug ID: 3722 Summary: check ssh key (and other parameters) before running the proxy command Product: Portable OpenSSH Version: 9.8p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

https://bugzilla.mindrot.org/show_bug.cgi?id=2695 Bug ID: 2695 Summary: inconsistent outout of "ssh.add -l" between ed25519 and rsa keys Product: Portable OpenSSH Version: 7.3p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component:

On 10/20/2014 07:34 PM, Toralf F?rster wrote: > I uploaded the screen shots from the virt-manager to [1] and [2] > > FWIW e56d9fccb was fine so the bug slipped in after that. > > > [1] http://www.directupload.net/file/d/3781/j9mwrtpq_jpg.htm > [2] http://www.directupload.net/file/d/3781/29trc56v_jpg.htm > It might be virtio-console related, when the uevetns are

On 10/20/2014 07:34 PM, Toralf F?rster wrote: > I uploaded the screen shots from the virt-manager to [1] and [2] > > FWIW e56d9fccb was fine so the bug slipped in after that. > > > [1] http://www.directupload.net/file/d/3781/j9mwrtpq_jpg.htm > [2] http://www.directupload.net/file/d/3781/29trc56v_jpg.htm > It might be virtio-console related, when the uevetns are

I'm wondering what's wrong with the follwoing command : tfoerste at n22 ~ $ wine regedit ~/Wine/dpi.reg regedit: setValue failed to open key System\CurrentControlSet\Hardware Profiles\Current\Software\Fonts tfoerste at n22 ~ $ cat Wine/dpi.reg [System\CurrentControlSet\Hardware Profiles\Current\Software\Fonts] "LogPixels"=dword:00000073 Pls reply to me too I'm not

https://bugzilla.samba.org/show_bug.cgi?id=8895 Summary: rsync warning: some files vanished Product: rsync Version: 3.0.9 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: toralf.foerster at gmx.de

I'm wonder whether this : tfoerste at n22 ~/devel/wine-git/dlls/secur32/tests $ make test ... ntlm.c:1343: Tests skipped: NTLM package not installed, skipping test ../../../tools/runtest -q -P wine -M secur32.dll -T ../../.. -p secur32_test.exe.so schannel.c && touch schannel.ok GnuTLS error: GnuTLS internal error. ... is wanted (schannel.ok is created in this case). I tested the

After reading this comment https://bugs.freedesktop.org/show_bug.cgi?id=30157#c5 I'm wondering whether the registry value in comment #4 of that bug report should be made a default value for wine or not ? -- MfG/Kind regards Toralf F?rster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

On 10/21/2014 06:40 PM, Josh Boyer wrote: > On Tue, Oct 21, 2014 at 12:10 PM, Toralf F?rster <toralf.foerster at gmx.de> wrote: >> On 10/20/2014 07:34 PM, Toralf F?rster wrote: >>> I uploaded the screen shots from the virt-manager to [1] and [2] >>> >>> FWIW e56d9fccb was fine so the bug slipped in after that. >>> >> >>>

On 10/21/2014 06:40 PM, Josh Boyer wrote: > On Tue, Oct 21, 2014 at 12:10 PM, Toralf F?rster <toralf.foerster at gmx.de> wrote: >> On 10/20/2014 07:34 PM, Toralf F?rster wrote: >>> I uploaded the screen shots from the virt-manager to [1] and [2] >>> >>> FWIW e56d9fccb was fine so the bug slipped in after that. >>> >> >>>

Hello, the following test case failed at my gen6too Linux using GnuTLS 3.0.3 : tfoerste at n22 ~/devel/wine-git/dlls/secur32/tests $ make test ../../../tools/runtest -q -P wine -M secur32.dll -T ../../.. -p secur32_test.exe.so schannel.c && touch schannel.ok GnuTLS error: An unexpected TLS packet was received. GnuTLS error: A TLS fatal alert has been received. schannel.c:748: Test

https://bugzilla.samba.org/show_bug.cgi?id=6578 Summary: put out skipped dirs files w/ perms and ownership Product: rsync Version: 3.0.5 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: toralf.foerster

Hello, just my opinion, but yesterday I run into a case, where after 7 hours of transferring a file (a little bit greater than 1 GB) the scp reported 100% and after that exited with an error (AIX 7.1): $ tsocks scp foo user at host:/tmp ... 100% 1101MB 44.2KB/s 448.0KB/s 7:05:38 scp: /tmp/foo: File too large Probably it should not be rounded up to 100% ? -- MfG/Sincerely Toralf F?rster

https://bugzilla.samba.org/show_bug.cgi?id=6577 Summary: man page mentioned http://lists.samba.org Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: toralf.foerster at gmx.de

Hi Kevin, Thanks for your quick response. The rsyncd.conf file looks like: charset = utf-8 [user] path = /c/user comment = "" use chroot = true uid = root gid = root read only = false auth users = admin I'm still confused about how to specify the path. The actual UNIX path is: /c/user/snapshots/rsync_test/last I've tried: --link-dest=snapshots/rsync_test/last

Hi all, I'm trying to figure out why a script works when using SSH but not when using the rsync protocol. When I run the following command: rsync -aPh --link-dest=/user/snapshots/rsync_test/last /home/user/rsync_test root at readynas.internal:/user/snapshots/rsync_test/Jan_11_2025 it works perfectly, correctly recognizing the link-dest parameter. However, when I try to run the same command

rsyncd doesn't take unix paths. You must adapt your --link-dest to contend with however the rsycd module is defined in rsyncd.conf. On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote: > Hi all, > > I'm trying to figure out why a script works when using SSH but not > when using the rsync protocol. When I run the following command: > > rsync -aPh

On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote: > Thanks for your quick response. The rsyncd.conf file looks like: > > charset = utf-8 > [user] > path = /c/user > comment = "" > use chroot = true Note the chroot... So "/" equals /c/user > uid = root > gid = root > read only = false > auth users = admin > > I'm