gmane.network.rsync.general archive

579 archived articles, newest first (page 2 of 6). Latest articles →

Re: rsync readonly mode?
Thu, 9 Apr 2026 06:33:18 -0500
Ryan Carsten Schmidt via rsync <[email protected]> • #29467
Re: rsync readonly mode?
Thu, 9 Apr 2026 07:43:19 -0400
Kevin Korb via rsync <[email protected]> • #29466
Re: rsync readonly mode?
Thu, 9 Apr 2026 13:14:08 +0200
RolandK via rsync <[email protected]> • #29465
Re: rsync readonly mode?
Wed, 8 Apr 2026 12:22:15 -0400
Kevin Korb via rsync <[email protected]> • #29464
rsync readonly mode?
Wed, 8 Apr 2026 18:18:05 +0200
RolandK via rsync <[email protected]> • #29463
Add --chmod-dest option for handling --fake-super permissions
Tue, 24 Mar 2026 09:39:00 +0000
Graham Leggett via rsync <[email protected]> • #29462
Re: rsync static builds 1.6.5 -> 3.4.1 - anyone ?
Sat, 14 Mar 2026 22:39:25 +0100
RolandK via rsync <[email protected]> • #29461
Re: rsync static builds 1.6.5 -> 3.4.1 - anyone ?
Sun, 8 Mar 2026 10:11:33 +0100
Roland privat via rsync <[email protected]> • #29460
Re: rsync static builds 1.6.5 -> 3.4.1 - anyone ?
Sun, 8 Mar 2026 05:48:23 +0000 (UTC)
matthew patton via rsync <[email protected]> • #29459
Re: rsync static builds 1.6.5 -> 3.4.1 - anyone ?
Sun, 8 Mar 2026 05:48:35 +0000 (UTC)
matthew patton via rsync <[email protected]> • #29458
rsync static builds 1.6.5 -> 3.4.1 - anyone ?
Sat, 7 Mar 2026 14:36:28 +0100
RolandK via rsync <[email protected]> • #29457
Re: Failed to find EVP_MD_CTX_copy function in openssl crypto lib.
Wed, 25 Feb 2026 20:28:58 +0100
RolandK via rsync <[email protected]> • #29456
Failed to find EVP_MD_CTX_copy function in openssl crypto lib.
Wed, 25 Feb 2026 20:01:05 +0100
RolandK via rsync <[email protected]> • #29455
Re: Copying one directory tree to another but exclude all top-level files
Fri, 30 Jan 2026 10:37:13 -0500
Kevin Korb via rsync <[email protected]> • #29454
Re: Copying one directory tree to another but exclude all top-level files
Fri, 30 Jan 2026 16:19:41 +0100
Paul Slootman via rsync <[email protected]> • #29453
Re: Copying one directory tree to another but exclude all top-level files
Fri, 30 Jan 2026 09:42:23 -0500
"Brian J. Murrell via rsync" <[email protected]> • #29452
Re: Copying one directory tree to another but exclude all top-level files
Fri, 30 Jan 2026 08:56:05 -0500
Kevin Korb via rsync <[email protected]> • #29451
Copying one directory tree to another but exclude all top-level files
Fri, 30 Jan 2026 08:23:06 -0500
"Brian J. Murrell via rsync" <[email protected]> • #29450
Re: Finally managed to get rsync script working after working on it for more than 7 hours since 1.30 AM on 28 Jan 2026 Wednesday
Thu, 29 Jan 2026 23:22:39 +0100
Roland privat via rsync <[email protected]> • #29449
Re: Precise meaning of initial 'h' when using -ii
Thu, 29 Jan 2026 17:18:23 -0500
"Brian J. Murrell via rsync" <[email protected]> • #29448
Re: Precise meaning of initial 'h' when using -ii
Thu, 29 Jan 2026 14:18:37 -0500
Kevin Korb via rsync <[email protected]> • #29447
Precise meaning of initial 'h' when using -ii
Thu, 29 Jan 2026 13:16:56 -0500
"Brian J. Murrell via rsync" <[email protected]> • #29446
Finally managed to get rsync script working after working on it for more than 7 hours since 1.30 AM on 28 Jan 2026 Wednesday
Thu, 29 Jan 2026 12:00:56 +0000
Turritopsis Dohrnii Teo En Ming via rsync <[email protected]> • #29445
ACLs are copied by UID rather than by Name
Fri, 16 Jan 2026 14:49:13 +0000
Chris Davies via rsync <[email protected]> • #29444
[Bug 11506] bug 6542 resurfaces: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.
Mon, 15 Sep 2025 09:00:35 +0000
just subscribed for rsync-qa from bugzilla via rsync <[email protected]> • #29443
[Bug 11506] bug 6542 resurfaces: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.
Mon, 15 Sep 2025 08:59:25 +0000
just subscribed for rsync-qa from bugzilla via rsync <[email protected]> • #29442
rsync didn't get server startup line (though the server does send a startup line)
Thu, 11 Sep 2025 20:49:09 +0800 (CST)
fzeli via rsync <[email protected]> • #29441
rsync --inplace doesn't stop if file is unwriteable
Fri, 29 Aug 2025 09:36:57 +0530 (IST)
Madhu via rsync <[email protected]> • #29440
Re: Slow large file copy
Thu, 31 Jul 2025 09:58:07 +0200
Gionatan Danti via rsync <[email protected]> • #29439
Re: Slow large file copy
Wed, 30 Jul 2025 14:26:20 +0200
Hardy via rsync <[email protected]> • #29438
Re: Slow large file copy
Wed, 30 Jul 2025 14:20:31 +0200
Gionatan Danti via rsync <[email protected]> • #29437
Re: Slow large file copy
Wed, 30 Jul 2025 08:49:17 +0200
Hardy via rsync <[email protected]> • #29436
Slow large file copy
Tue, 29 Jul 2025 12:55:20 +0200
Gionatan Danti via rsync <[email protected]> • #29435
Symbolic Link Permissions on OpenBSD
Sun, 8 Jun 2025 01:20:19 -0600
Antoine Verheijen via rsync <[email protected]> • #29434
/include/config/.PINCTRL_EMMITSBURG.fUespu","security.selinux") failed: Operation not supported (95)
Tue, 13 May 2025 18:54:45 +0200
Mario Marietto via rsync <[email protected]> • #29433
Re: rsync --chmod affects the source permissions as well as destination permissions
Mon, 5 May 2025 21:32:23 +0100
Graham Leggett via rsync <[email protected]> • #29432
Re: rsync --chmod affects the source permissions as well as destination permissions
Mon, 5 May 2025 15:14:03 -0400
Derek Martin via rsync <[email protected]> • #29431
Re: How do I restore using --fake-super?
Mon, 21 Apr 2025 10:58:12 +0100
Graham Leggett via rsync <[email protected]> • #29430
Re: How do I restore using --fake-super?
Mon, 21 Apr 2025 07:37:07 +0200
TheNew HEROBRINE via rsync <[email protected]> • #29429
Re: rsync --chmod affects the source permissions as well as destination permissions
Wed, 16 Apr 2025 16:10:56 +0100
Graham Leggett via rsync <[email protected]> • #29428
rsync --chmod affects the source permissions as well as destination permissions
Tue, 8 Apr 2025 12:54:24 +0100
Graham Leggett via rsync <[email protected]> • #29427
Re: How do I restore using --fake-super?
Tue, 8 Apr 2025 11:34:09 +0100
Graham Leggett via rsync <[email protected]> • #29426
Re: How do I restore using --fake-super?
Tue, 8 Apr 2025 10:28:32 +0100
Graham Leggett via rsync <[email protected]> • #29425
Re: How do I restore using --fake-super?
Tue, 8 Apr 2025 11:04:42 +0200
Paul Slootman via rsync <[email protected]> • #29424
How do I restore using --fake-super?
Tue, 8 Apr 2025 08:48:14 +0100
Graham Leggett via rsync <[email protected]> • #29423
RE: [Question] Building without iconv
Tue, 4 Mar 2025 10:14:37 -0500
"Randall S. Becker via rsync" <[email protected]> • #29422
Re: [Question] Building without iconv
Mon, 3 Mar 2025 22:27:57 -0500
Kevin Korb via rsync <[email protected]> • #29421
RE: [Question] Building without iconv
Mon, 3 Mar 2025 21:55:00 -0500
"Randall S. Becker via rsync" <[email protected]> • #29420
Re: [Question] Building without iconv
Mon, 3 Mar 2025 19:14:06 -0700 (Mountain Standard Time)
Marc Aurèle La France via rsync <[email protected]> • #29419
[Question] Building without iconv
Mon, 3 Mar 2025 20:53:29 -0500
"Randall S. Becker via rsync" <[email protected]> • #29418
buffer overflow in recv_file_entry
Tue, 18 Feb 2025 12:09:36 +0100
Jakob Unterwurzacher via rsync <[email protected]> • #29417
Re: Create "thincopy": with fileystem metadata only?
Tue, 18 Feb 2025 10:20:11 +0100
"Peter B. via rsync" <[email protected]> • #29416
Re: Create "thincopy": with fileystem metadata only?
Sun, 16 Feb 2025 13:46:34 +0000
Stein Vidar Hagfors Haugan via rsync <[email protected]> • #29415
Re: Create "thincopy": with fileystem metadata only?
Sun, 16 Feb 2025 13:39:23 +0000
Stein Vidar Hagfors Haugan via rsync <[email protected]> • #29414
Re: Create "thincopy": with fileystem metadata only?
Sat, 15 Feb 2025 21:24:17 +0100
"Peter B. via rsync" <[email protected]> • #29413
pre/post-xfer: How to distinguish between up- and download?
Fri, 14 Feb 2025 09:36:46 +0100
Frank Thommen via rsync <[email protected]> • #29412
patches - Re: new release 3.4.0 - critical security release
Sun, 19 Jan 2025 10:08:57 +0530 (IST)
Madhu via rsync <[email protected]> • #29411
Re: question about the recursive algorithm
Thu, 16 Jan 2025 22:02:31 +0000
bp25--- via rsync <[email protected]> • #29410
Re: question about the recursive algorithm
Thu, 16 Jan 2025 10:23:38 -0500 (EST)
Kevin Korb via rsync <[email protected]> • #29409
Re: question about the recursive algorithm
Thu, 16 Jan 2025 15:16:02 +0000
bp25--- via rsync <[email protected]> • #29408
Re: question about the recursive algorithm
Thu, 16 Jan 2025 09:55:32 -0500 (EST)
Kevin Korb via rsync <[email protected]> • #29407
Re: question about the recursive algorithm
Thu, 16 Jan 2025 14:47:27 +0000
BP25 via rsync <[email protected]> • #29406
Re: question about the recursive algorithm
Thu, 16 Jan 2025 09:15:37 -0500 (EST)
Kevin Korb via rsync <[email protected]> • #29405
Re: question about the recursive algorithm
Thu, 16 Jan 2025 07:17:07 -0700 (Mountain Standard Time)
Marc Aurèle La France via rsync <[email protected]> • #29404
question about the recursive algorithm
Thu, 16 Jan 2025 13:53:04 +0000
BP via rsync <[email protected]> • #29403
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 16:54:10 -0700
"Nelson H. F. Beebe via rsync" <[email protected]> • #29402
rsync 3.4.1 released
Thu, 16 Jan 2025 08:24:55 +1100
"rsync.project via rsync" <[email protected]> • #29401
Re: new release 3.4.0 - critical security release
Thu, 16 Jan 2025 06:48:42 +1100
"rsync.project via rsync" <[email protected]> • #29400
RE: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 14:18:19 -0500
"Randall S. Becker via rsync" <[email protected]> • #29399
RE: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 14:17:07 -0500
"Randall S. Becker via rsync" <[email protected]> • #29398
Re: new release 3.4.0 - critical security release
Thu, 16 Jan 2025 06:10:58 +1100
"rsync.project via rsync" <[email protected]> • #29397
RE: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 09:20:30 -0500
"Randall S. Becker via rsync" <[email protected]> • #29396
RE: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 08:21:01 -0500
"Randall S. Becker via rsync" <[email protected]> • #29395
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 18:02:16 +1100
"rsync.project via rsync" <[email protected]> • #29394
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 17:57:45 +1100
"rsync.project via rsync" <[email protected]> • #29393
Re: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 20:20:21 -0800
Perry Hutchison via rsync <[email protected]> • #29392
RE: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 22:55:24 -0500
"Randall S. Becker via rsync" <[email protected]> • #29391
RE: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 22:35:02 -0500
"Randall S. Becker via rsync" <[email protected]> • #29390
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 10:53:15 +1100
"rsync.project via rsync" <[email protected]> • #29389
RE: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 18:46:29 -0500
"Randall S. Becker via rsync" <[email protected]> • #29388
Re: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 17:12:02 -0600
Ryan Carsten Schmidt via rsync <[email protected]> • #29387
RE: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 18:09:08 -0500
"Randall S. Becker via rsync" <[email protected]> • #29386
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 09:34:10 +1100
"rsync.project via rsync" <[email protected]> • #29385
Re: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 15:57:39 -0600
Ryan Carsten Schmidt via rsync <[email protected]> • #29384
Re: new release 3.4.0 - critical security release
Wed, 15 Jan 2025 08:31:02 +1100
"rsync.project via rsync" <[email protected]> • #29383
RE: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 15:16:30 -0500
"Randall S. Becker via rsync" <[email protected]> • #29382
Re: new release 3.4.0 - critical security release
Tue, 14 Jan 2025 20:00:29 +0000
Charalampos Mitrodimas via rsync <[email protected]> • #29381
new release 3.4.0 - critical security release
Wed, 15 Jan 2025 06:49:04 +1100
"rsync.project via rsync" <[email protected]> • #29380
Re: question about --link-dest and the rsync protocol
Sun, 12 Jan 2025 16:28:15 -0600
Anthony LaTorre via rsync <[email protected]> • #29379
Re: question about --link-dest and the rsync protocol
Sun, 12 Jan 2025 15:36:51 +0100
Paul Slootman via rsync <[email protected]> • #29378
Re: question about --link-dest and the rsync protocol
Sun, 12 Jan 2025 09:16:21 +0100
Hardy via rsync <[email protected]> • #29377
Re: question about --link-dest and the rsync protocol
Sat, 11 Jan 2025 21:23:53 -0600
Anthony LaTorre via rsync <[email protected]> • #29376
Re: question about --link-dest and the rsync protocol
Sat, 11 Jan 2025 22:01:21 -0500
Kevin Korb via rsync <[email protected]> • #29375
question about --link-dest and the rsync protocol
Sat, 11 Jan 2025 20:52:09 -0600
Anthony LaTorre via rsync <[email protected]> • #29374
Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
Tue, 24 Dec 2024 10:28:17 +0100
Hardy via rsync <[email protected]> • #29373
Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
Tue, 24 Dec 2024 10:00:58 +0100
Hardy via rsync <[email protected]> • #29372
Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
Tue, 24 Dec 2024 09:53:08 +0100
Mario Marietto via rsync <[email protected]> • #29371
Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
Mon, 23 Dec 2024 23:02:21 +0100
Mario Marietto via rsync <[email protected]> • #29370
Re: rsync: [sender] read errors map ping "file" : Input/output error (5)
Tue, 24 Dec 2024 11:24:50 +1200
Tomasz Ciolek via rsync <[email protected]> • #29369
Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
Mon, 23 Dec 2024 22:06:47 +0100
Mario Marietto via rsync <[email protected]> • #29368
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.