Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[BackupPC\-users\]\s+Interrupted\s+rsyncd\s+backups\s+on\s+Backuppc4\s+and\s+rsyncTMP\.XXXX\s+files\,\s+these\s+files\s+never\s+get\s+cleaned\s+out\.\s*$/: 3 ]

Total 3 documents matching your query.

1. [BackupPC-users] Interrupted rsyncd backups on Backuppc4 and rsyncTMP.XXXX files, these files never get cleaned out. (score: 1)
Author: Mike Dresser <mdresser_l AT windsormachine DOT com>
Date: Tue, 31 Jan 2017 15:45:09 -0500
One thing I've noticed on backuppc 4.0.0alpha3 is that if an rsyncd backup is interrupted(server crash, someone rebooted the server, etc), it leaves behind a rsyncTmp.pid.y.z file in the main host di
/usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2017-01/msg00079.html (11,966 bytes)

2. Re: [BackupPC-users] Interrupted rsyncd backups on Backuppc4 and rsyncTMP.XXXX files, these files never get cleaned out. (score: 1)
Author: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
Date: Wed, 1 Feb 2017 09:53:40 +1100
Thank you, this is so true... I just found: client 1: 20 x 1125MB client 2: 38 x 8639MB client 3: 20 x 3565MB client 4: 19 x 8639MB client 5: 97 x 100MB client 6: 42 x 34MB client 7: 7 x 4101MB clien
/usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2017-01/msg00080.html (13,655 bytes)

3. Re: [BackupPC-users] Interrupted rsyncd backups on Backuppc4 and rsyncTMP.XXXX files, these files never get cleaned out. (score: 1)
Author: Mike Dresser <mdresser_l AT windsormachine DOT com>
Date: Wed, 1 Feb 2017 12:17:05 -0500
Now that I've poked this again, even a network error such as the client went away while backup was in progress will leave behind these files. A really unstable client could leave a lot of orphan rsyn
/usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2017-02/msg00005.html (11,373 bytes)

Current List: 1 - 3
Page: [1]
This search system is powered by Namazu