ith one caveat:
>
> You must always make sure the source drive is intact and ok. If not, and
> you back it up anyway, then you are already toast (you will overwrite
> your last backup with new faulty data).
>
> There's several approaches to how to do the transfer:
>
>
Am Tue, Aug 03, 2021 at 07:10:03AM +0800 schrieb William Kenworthy:
> >> Keep in mind that both repos have the same ID - you should also rsync
> >> the cache and security directories as well as they are now out of sync
> >> (hence the warning).
> > That thought c
Rich Freeman wrote:
> On Tue, Apr 12, 2022 at 1:08 PM Dale wrote:
>> I remounted the drives and did a backup. For anyone running up on this,
>> just in case one of the files got corrupted, I used a little trick to
>> see if I can figure out which one may be bad if
e ago. I tried again
>> with my usual command, it wants to update everything again. I seem to
>> recall that rsync goes by file size and modify time stamps. Is there a
>> way to make the NAS box files newer or something so that it will not try
>> to copy the same f
he client can then do it's backup and rsync it over to the server
>> when it's done, and that push can be done as a regular user on both ends. The
>> actual backing up on the client must be done by root of course, no other user
>> has the necessary access.
>
>
copy" will not contain any "sub-mounts" (as if you
> > accessed it from a livecd),
>
> Or you could simply use the -x option with rsync. But copying an in use
> filesystem is a bad idea, better to boot from a live CD and do the job
> there. If you want to minimise do
> I guess I have to run emerge sync and emerge -uD world on each client
> still,
> but they use the http replicator instead of gentoo servers for both
> updating the portage/rsync files and downloading the distfiles (via the
> http
> replicator)?
In the case of distfiles
A. Khattri bway.net> writes:
>
> On Wed, 13 Jul 2005, James wrote:
>
> > Ahhh that's it:
> > # cat /usr/portage/metadata/timestamp
> > Tue Jul 12 13:06:52 UTC 2005
> > # date
> > Wed Jul 13 12:05:26 UTC 2005
>
> On my machines, the mast
for each client).
>
> The problem is with portage logs: I can not find any pattern
> I could use to filter them out. For example, this is small part
> of /var/log/emerge.log:
>
> 1250923552: *** emerge sync
> 1250923552: === sync
> 1250923552: >>> Starting r
Nikos Chantziaras wrote:
> Alan McKinnon wrote:
>> On Friday 26 December 2008 21:49:02 Nikos Chantziaras wrote:
>>
>>> OK, I once again verified that fragmentation seems to be a big issue
>>> even on Linux. I just migrated to ext4, and in order to do that I had
&g
Hi Liviu,
it seems you're only allowed to access web, FTP and rsync services on
the Internet through your proxy. Both rsync and NTP use their own ports
and protocols, different from HTTP/FTP/rsync. Firstly, you need a proxy
server (or some other form of tunnel) that will allow for rdat
e --sync makes a call to rsync program ? I did not take the time
> yet to learn more about Gentoo specific softwares, but I will do that
> soon. Look at the sizes format in bytes. Today it often happens -well,
> most of the time- several Mo of download, so the byte unit is not very
>
to a drive in good condition
(all other things being equal).
I have a setup with 3 machines, 1 with very OLD HDs. I'm behind a
firewall, so I can't use rsync protocol over the web, I download a
portage snapshot daily and use local rsync, the 2 other machines use
the one synced locally
On Sun, Dec 2, 2012 at 9:21 AM, Randy Westlund wrote:
> I've been using rsync to sync binary files, shell scripts, my
> workspace, and random user files under my home directory across
> multiple machines. I'm using one server as the master copy, which
> makes daily inc
> and on the first computer
> cat /dev/hda1 | pv | gzip | nc othermachine
Wow.. That's a cool way to do things.
The other way to do it, without having the need to use nc (netcat) would
be to use ssh instead. I do it either
1. tar -cf / . | ssh [EMAIL PROTECTED] "tar -xvf -
fo, warn or error.
There's also enotice - although I think its deprecated?
A crude way of only checking the warning log files is by making a
judgment call on their size:
=
-rw-r--r-- 1 rootportage 18944 May 6 12:12 3799-rsync-2.6.8.log
-rw-r--r-- 1 rootp
On 05/07/18 02:32, gevisz wrote:
> 2018-07-04 21:01 GMT+03:00 Mick :
>> On Wednesday, 4 July 2018 18:57:56 BST gevisz wrote:
>>> 2018-07-04 11:55 GMT+03:00 Alex Thorne :
>>>>> I use rsync and get the following for more than a day now;
>>>>>
>&
2015-08-09 19:05 GMT-06:00 Rich Freeman :
> TL;DR - don't worry about it too much, but don't be surprised if
> emerge --sync doesn't give you anything new for a day or two
.
The rsync git mirror on github is up arlready I have been using this,
for some months, and has been
th new faulty data).
There's several approaches to how to do the transfer:
If you have say a general fileserver with lots of files that don't
change much or often, just rsync everything in one go. There is no
optimization you can do that will perform much faster than rsync.
If you have a
]
main-repo = gentoo
[gentoo]
location = /usr/portage
sync-type = rsync
sync-uri = rsync://rsync.gentoo.org/gentoo-portage
auto-sync = yes
sync-rsync-verify-metamanifest = no
# for daily squashfs snapshots
#sync-type = squashdelta
#sync-uri = mirror://gentoo/../snapshots/squashfs
=
c
nce the symlink will be broken.
>
> Indeed. And the failure that produces is not at all graceful.
>
> I spent a little time trying to figure out where in the Wiki or docs
> that the rsync -> git migration steps should be documented, but I
> didn't find anyplace that looked like t
Wols Lists wrote:
> On 18/12/2022 22:11, Dale wrote:
>> Wol wrote:
>>> On 18/12/2022 18:59, Dale wrote:
>>>> Since this is local, I just use rsync to do my backups. I did have to
>>>> change the options a bit. It seems TrueNAS doesn't like some of
or no
> maintainers in case of herds requested to be disbanded.
>
> 24 Jan 2016; Michał Górny metadata.xml:
> Set appropriate maintainer types in metadata.xml (GLEP 67)
>
> What is the approved method of reading change-logs nowadays?
If you are using git sync, just go
ot;reasons". I'd like to switch to rsync
and run it more often. I've done the RTFM, but I'd more eyes to check
this out before the first run.
I haven't yet set up my system, but a couple of tweaks I'm planning to
add ...
Either use btrfs, or an lvm partition,
On Wed, Mar 26, 2008 at 1:25 PM, Dirk Heinrichs <[EMAIL PROTECTED]>
wrote:
> Am Mittwoch, 26. März 2008 schrieb ext Kaushal Shriyan:
> > I am running the command
> >
> > /usr/bin/rsync -avO /var/lib/mysql [EMAIL PROTECTED]:/var/lib/ >
> > /tmp/rsync-${TIMESTAMP
231
>
The bug has been fixed.
> The cache format changed between portage-2.0.x and portage-2.1.x, so
> emerge --metadata needs to be run in order to migrate to the new
format.
>
Now that my rsync local server has been upgraded to portage 2.1.2.2,
should I still keep
PORTAGE_RS
unix-like (not vfat or ntfs) i'd prefer
using "rsync -a" to doing this job.
but if you have any doubt... the manual is your friend. ;)
man tar
man rsync
man cp
[]'s
.m
--
[EMAIL PROTECTED] mailing list
tion.
My actual approach would be to set up the laptop as an rsync mirror, then:
laptop $ emerge --sync
(connect laptop to null-internet box via crossover cable + sync from laptop)
nointernet $ emerge --sync
nointernet $ emerge -pvfuDN world > getfile
(copy getfile to laptop, move laptop
hould have been loaded in with an emerge --sync? or an rsync of the
> > whole tree from one of the mirrors?
>
> emerge --sync
Thanks for the help. Turned out I had set up the module definition wrong in
my rsyncd.conf. I've now got both emerge --sync working using this as the
sy
On Thu, 03 Nov 2005 19:41:19 -0500, Dave Nebinger wrote:
> I guess really what I'm saying is no, it is not a good idea. There's
> plenty of other backup solutions out there that would work better than
> this scheme. If you have a server and space for the file, rsync would
his) symbol"and it cannot detect alsa module setting,so it use all. but my alsa is not use a module,it in the kernel.
!!! Rsync has not successfully finished. It is recommended that you keep
!!! trying or that you use the 'emerge-webrsync' option if you are unable
!!! to use
On 2018-07-05, Grant Edwards wrote:
> As of today, I seem to be unable to a an "emerge --sync".
>
> The process either hangs forever at the "Refreshing keys from keyserver step:
[...]
> Or, it fails because there are no public key to verify a manfest:
For now, I&#x
rder to boot proplery.
Sorry if I am maybe a bit OT (am I?):
I often cloned systems from or into VMs by booting both systems with
live-CDs, mounting their disks and "rsync -av" the root-fs over ...
sure, taking care of dev/sys/proc/tmp does not hurt ...
After the rsync maybe some fstab-editing
Am 01.10.2013 14:32, schrieb Nicolas Sebrecht:
> The 01/10/13, Stefan G. Weichinger wrote:
>
>> I used split and tar to split the image-file into 100 MB parts and rsync
>> them over right now.
>>
>> Maybe I have something wrong in my kernel ... the server shows a
Martin Vaeth wrote:
> Simon Thelen wrote:
> > I sync from git and none of my Manifests track the ebuilds, so this
> > could be a thing.
>
> No. git has (probably, I didn't check)
> thin-manifests = true
> in its metadata/layout.conf, but for rsync this shoul
On Thu, 12 Dec 2013 18:06:40 -0800, Grant wrote:
> I may end up using portage instead of rsync but I think I'd like to
> try rsync first. Am I setting myself up for failure?
Tried and tested system maintenance tool vs. home brewed modification of
critical files... I'd say a defi
On 14/10/2021 09:28, Miles Malone wrote:
So the default being for git to act like git, instead of git to act
like an alternative to rsync, makes perfect sense in that context.
And once it's sync'd the first time, I think sync depth is ignored. It
normally doesn't make much di
On 30/01/2024 19:19, Rich Freeman wrote:
I'd echo the other advice. It really depends on your goals.
If you just want a simple backup, I'd use something like rsync onto lvm
or btrfs or something. I've got a little script that sticks today's date
onto the snapshot na
On Tue, Jan 30, 2024 at 3:08 PM Wol wrote:
>
> On 30/01/2024 19:19, Rich Freeman wrote:
> > I'd echo the other advice. It really depends on your goals.
>
> If you just want a simple backup, I'd use something like rsync onto lvm
> or btrfs or something. I
uff between boxes with rsync via ssh. Simple
> enough and it seems to be working fine.
I use a similar setup for LXC containers running over a gentoo box,
except that my box is setted up to publish the binary packets on a
specified directory that is accessible via HTTP. My LXCs take the binary
pac
;>> the master are: /etc/conf.d/hostname, /etc/conf.d/net,
>>> /etc/ssh/sshd_config, /etc/shorewall/*. I write comments in those
>>> files which serve as flags for scripted changes.
>>>
>>> I write a script that is run from the master to the submaster, o
t; It looks like repoman is the culprit
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=598376
>>
>
> This is probably not the issue here, since Gentoo uses thin manifests
> (there is nothing for repoman to update). The manifests that are
> causing the problem aren'
-a . ../
Seems to me slow but correct? Or?
cp -a is fine although, in my experience, I've found that rsync is more
reliable:
rsync -av /mnt/oldrootfs/. /mnt/newrootfs/.
Note that -a covers almost everything but you may need the following
additional options depending on how your files
After a lot of testing and testing of different methods to make backups I
reached a conclution of what I need, but I don't know if it's possible.
I want to do an rsync of the server directories I want but locally, it should
end up in a tared file (it doesn't need to be compressed
ou don't even get a root password even if you by it.
> I can export directories with nfs witch i have done and so a Gentoo server
> in the middle can sync the data between the two machines.
Correct me if I'm wrong, but can't you use rsync or ssh from the
gentoo server i
On 23:29 Tue 11 Mar , Logan McKenna wrote:
> I just use mkstage4.sh which can be found on the forums. Works great for me
>
> On Tue, Mar 11, 2008 at 11:10 PM, forgottenwizard <
> [EMAIL PROTECTED]> wrote:
>
> > I'm messing around with doing backups via rsy
er dmcrypt,
> loopback-mounted from a file, followed by an rsync over ssh to a remote
> host), and I'd be happy to find something better!
I'm currently using it with a local server. If I decide to use the
backups on a remote server too, I'll probably stick to backing up to the
alled "tar" is the tool to use.
>
> But if a backup to disk is done, tar is still a good tool for the job,
> but IMO not the best tool available. Instead I'd suggest to use rsync.
> Reason: It's easier to restore just a single file.
>
> It's of course
our friend... :-)
>
Another option is to nfs-mount the client's hard drive on the fast
box, bind a portage tree into the filesystem, chroot & proceed to
emerge.
Or you could build the whole filesystem on the server, and push changes
out to the client with rsync or some such thing. I
On Mon, 2007-11-05 at 07:34 -0330, Roger Mason wrote:
> Shawn Haggett <[EMAIL PROTECTED]> writes:
>
> > Roger Mason wrote:
> >> I have passwordless ssh between mymachine and backup_machine and the
> >> rsync command in the crontab runs perfectly from the comma
/
*EXCEPT* /dev, /proc, /sys and /lost+found)
mkdir /root/hd/dev
mkdir /root/hd/proc
mkdir /root/hd/sys
Or replace all this with one command
cp -al / /root/hd
I assume you meant 'cp -ax' :P
That's indeed faster than typing everything by hand and I forgot about it ;P
or,
On Tue, 15 Jul 2008 08:52:20 +0100
Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Tue, 15 Jul 2008 10:42:20 +0300, Nikos Chantziaras wrote:
>
> > I assume you meant 'cp -ax' :P
>
> I did, it's tar that uses -l for this.
>
> > > rsync -ax / /roo
ently I would have to produce an md5sum of all files in
> > /etc /usr /var and / and compare these. But there are dozens of
> > thousands of files in these directories.
>
> You could use rsync with –dry-run to tell you what's different
> (without actually transferring any file
%s%s%s/" % (user_name, ip, port), 1))
>
> Probably needs to be reported.
>
>
>
>
Coding against PEP8 is not a bug. I guess devs find string
concatenation more handy and maintainable.
The bug was about the addrinfos data gotten from the server. I thought
the response of
igrate to a 2T
>>> Sata disk. This is simple, but, I have a few caveats.
> [...]
>> Now just rsync everything in /mnt/sda* to the right place in /mnt/sdb
>
> Some weeks ago, I did this kind of migration. I ended up using good ol'
> tar - after lots of research, it was
OW.
> > So you should install/use cdb, which makes the whole rsync/update process
> > REAL FAST.
> >
> >>If you sync regularly it's usually within 5 min.
> >
> > it is, with cdb.
>
> Thanks for the hint.
> If I got it right here's the link fo
On 9/15/05, aka Sevein Jes__s Garc__a Crespo <[EMAIL PROTECTED]> wrote:
> Hi! Was Portage developed to work with a /usr/portage directory mounted
> from another computer with NFS or SMB? I did it and it worked.
>
> I thought this way could be easier than rsync when you have ma
Why would you want ALL of distfiles? A lot is old & redundant.
Also why would you rsync it? Thats a lot of cpu grinding.
I suggest setting up one of these:
http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator
If someone really wants every source file ever made, this will
rity patches - can we
| *safely* assume that if the GLSA is out, that the updated versions are
| available?
Under normal circumstances, CVS to rsync runs every half hour, with up
to an hour and a half(?)'s lag depending upon which rsync mirror you
use. As for commits, most of us are European or
I would recommend creating a new file system on the destination drive.
The do a rsync -axH src dst
Then install grub on the master boot sector on the destination drive
as specified in the gentoo installation manual.
I have had problems with dd ghosting in the past but rsync has worked
flawlessly so far.
Jimmy
--
gentoo-user@gentoo.org mailing list
Hi guys,
I'm just curious about something. I've noticed many people report
problems with their repository syncing simply because someone was in
the middle of committing to the repository. Couldn't this be resolved
by replacing the syncing mechanism with *svn* as opposed to rsync
>> My backup user needs a shell on the backup server in order to execute
>> rsync and needs to be included in /etc/ssh/sshd_config AllowUsers in
>> order to SSH in. My authorized_keys file is locked-down. The second
>> field for the user in /etc/shadow is an exclamatio
Am 30.09.2013 22:03, schrieb Stefan G. Weichinger:
> I will simply let the scp take its time over night ... and I hope the
> KVM-performance will be OK when I start the converted VM.
I used split and tar to split the image-file into 100 MB parts and rsync
them over right now.
Maybe
On Tue, Oct 1, 2013 at 7:20 AM, Bruce Hill
wrote:
> There are 3 (or more) computers which sync (sometimes daily) on my LAN at
> work: server, router, and workstation. server has issues almost all the time
> getting a rsync server (for lack of better way to state it). All three comps
&
Alan Mackenzie wrote:
>!!! /usr/portage/sys-apps/busybox/busybox-.ebuild
>!!! Got: 8493
>!!! Expected: 8580
Do you use the default (rsync) for syncing, or have you changed
the method?
I have the above claimed filesize (8493), but the Manifest
I obtained from rsync i
flag needs to be OFF.
I have:
sys-process/vixie-cron-4.1-r14 (pam -debug -selinux)
I created a cron job as root:
6 18 3 * 1-5 rsync -av /usr/src/linux/.config
/home/thelma/backup/etc/etc_atom/kenel-config
and checking the /var/log/messages it run at 18:06 today (Mar.21) ?
but it should run every
to mount a location that can be accessed
>>> via ssh to your local file system, as if you are using ssh.
>>>
>>
>> In a similar vein, scp.
>
> And considering something still robust but a little more smart, rsync.
>
I was actually going to come back and suggest rscync over ssh. I
didn't originally mention it because I typically associate rsync with
backups.
Am 18.09.2014 um 18:44 schrieb Joseph:
> I want to run a cron job only once a month. The problem is the computer is
> only on on weekdays Mon-Fri. 1-5
> cron tab as this below is an "or" condition as it has entries in Days of the
> Months and Day of the Week
>
On dim. 23 févr. 11:11:31 2020, Ian Zimmerman wrote:
> emerge-webrsync has just eaten my /usr/portage :-( ;-(
>
> I let it run unattended. When I came back I saw first some complaints
> from rsync about "vanished" files ... something like
>
> /usr/portage/_build has
On Sun, 5 Apr 2020 13:08:08 -0500, Dale wrote:
> If you are using rsync or cp -u you could start the copy then stop at it
> certain points to let the SSD cool, then start it again. It will
> basically pick up where it left off.
Don't use cp -u, if you interrupt it while a file i
which involve complicated or
expensive fixes:
In a worst-case, you could try skipping manifest verification
altogether on the affected machine. You must do 2 steps to get that
working.
1) In /etc/portage/repos.conf/gentoo.conf set...
sync-rsync-verify-metamanifest = no
The default installed sett
is problem over here, but on rare occasions. Leaving it for
> > half a day usually fixes it. Have you tried a different rsync mirror?
> > You can use 'mirrorselect -i -r' for this task.
>
> I used to see this from time to time, but then I switched to using git
> ins
Yesterday I switched my gentoo repo from rsync to git, and the initial
--sync with an empty directory did a git clone successfully.
Today, when I try to sync, it always fails:
$ sudo emerge --sync >>> Syncing repository 'gentoo' into
'/var/db/repos/gentoo'..
t
commands are concerned. I don't think you can create reflinks between
subvolumes either.
The files are already reflinked by design though. You'd just make a
new snapshot and then rsync over it. Anything that doesn't change
will already share space on disk by virtue of the snapsho
On 2023-06-09, Daniel Pielmeier wrote:
> If it is only about gemato then temporary disable the rsync-verify flag
> which pulls it in.
>
> # USE="-rsync-verify" emerge sys-apps/portage
The problem I ran into is that you never know how many issues there
are standing in the
Hello list.
My local rsync server has been upgraded to the 2006.1 profile
(gcc-4.2.2). All my other boxes that sync against the local server have
problems with missing digest files.
I follow the instructions in
http://gentoo-wiki.com/HOWTO_Local_Rsync_Mirror and
http://www.gentoo.org/doc/en
Alan E. Davis wrote:
>
>I'm not certain what an rsync server is, but I am guessing it
>would be a cache of files that could be picked up by other machines.
>
>
When you do a emerge sync, it connects to a rsync server. When I do
that on one of my secondary rigs, it gets t
rhaps I'm sorely mistaken) appeared to be faster using git
than rsync -- hence my choice of git over rsync (the discussion at
https://forums.gentoo.org/viewtopic-t-1009562.html shows me to not be
alone in this experience).
Having the changelogs available also comes off as a positive for me --
On Fri, Jul 6, 2018 at 4:34 AM Davyd McColl wrote:
>
> I understand that git history will build over time -- I'm less concerned
> with (eventual) disk usage than I am with the speed of `emerge --sync`,
> which (and perhaps I'm sorely mistaken) appeared to be faster using git
ots, for YEARS?
> >
> > My comment was based on using rsync to copy from the source to the backup
> > filesystem.
>
> Well, that's EXACTLY what I'm doing too. NO DIFFERENCE. Actually, there
> is a minor difference - because I'm using lvm, I'm al
: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
volatile: False
sync-rsync-verify-max-age: 3
sync-rsync-verify-metamanifest: yes
sync-rsync-extra-opts:
sync-rsync-verify-jobs: 1
Binary Repositories
o
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.7::gentoo (virtual/os-headers)
sys-libs/glibc: 2.31-r3::gentoo
Repositories:
gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-r
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-verify-jobs: 1
sync-rsync-extra-opts:
sync-rsync-verify-metamanifest: yes
sync-rsync-verify-max-age: 24
ACCEPT_KEYWORDS="amd64"
ACCE
n a secure manner.
>
Sure, but this also doesn't support signature verification at all (at
least not by portage - git can of course manually verify any commit),
so your points still don't apply.
> > and as a bonus they want them prepended to
> > instead of appended so that r
d replace fstab and grub.conf on the backup
> medium and blacklist them from the files which you want to back up.
why wouldn't I backup fstab and grub.conf as well? If my internal disk
dies, I assume I'll swap them over, meaning grub and fstab will have to
be the same.
> Concer
ery byte of the source drive, not jut the ones in use). Although I have
> used this method, I wouldn't do it again, I'd set up the partitions,
> copy with rsync and run grub to install it on the new drive.
Right I'm going to do it this way, in the morning, so if I'm wrong
?
You cannot use tar unless you create an exclude file, as it will copy
the contents of /dev and /sys, which means the entire contents of RAM,
and anything that is currently being generated by your devices will be
copied as well.
Personally, I would use either tar or rsync to do this, however, in
sa
> >> NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE
> >> !!
> >> !!
> >>
> >> If you are seeing this message, you are not in
> >> the right place. Please check our website
> >> http://mirror.arcticnetwork.ca for
way to do it, without having the need to use nc (netcat) would
> be to use ssh instead. I do it either
>
> 1. tar -cf / . | ssh [EMAIL PROTECTED] "tar -xvf - -C /"
Whoops.. should be
tar -cf - / | ssh -c blowfish [EMAIL PROTECTED] "tar -xvf - -C /"
> 2. rs
Hi! Was Portage developed to work with a /usr/portage directory mounted
from another computer with NFS or SMB? I did it and it worked.
I thought this way could be easier than rsync when you have maybe two
or three computer working with the same network-shared directory. But I
noticed a poor
On 12/5/05, Dale <[EMAIL PROTECTED]> wrote:
>
> If you have several Gentoo rigs, you can also set up a rsync server.
> You actually already have it but it is not turned on. Search for rsyncd
> on the forums in the Documentation, Tips & Tricks
I have three machines w
On 03/21/2018 11:36 AM, Neil Bothwick wrote:[snip]
>> rsync -av --delete /Monday/Images/O/OSMANFathia2946/
>> thelma@10.10.0.6:/Monday/Images/O/OSMANFathia2946/ sending incremental
>> file list rsync: failed to set times on
>> "/Monday/Images/O/OSMANFathia2946/.
On Wednesday, 4 July 2018 19:32:33 BST gevisz wrote:
> 2018-07-04 21:01 GMT+03:00 Mick :
> > On Wednesday, 4 July 2018 18:57:56 BST gevisz wrote:
> >> 2018-07-04 11:55 GMT+03:00 Alex Thorne :
> >> >> I use rsync and get the following for more than a day n
>>>> My backup user needs a shell on the backup server in order to execute
>>>> rsync and needs to be included in /etc/ssh/sshd_config AllowUsers in
>>>> order to SSH in. My authorized_keys file is locked-down. The second
>>>> field for the use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/30/2013 06:22 AM, Neil Bothwick wrote:
> On Mon, 30 Sep 2013 12:01:27 +0200, Hinnerk van Bruinehsen wrote:
>
>>> mount /usr -o remount,ro mkdir /newusr rsync -a /usr/ /new/usr/ Comment out
>>> /usr line in
>>&
the original one).
>
> This was never intended to be a user-visible change (hence no news,
> etc). The digest issue was an oversight which was fixed. At this
> point rsync should work as it always did, minus one really long sync.
>
> The main thing you'll probably see is
new Manifest and Changelog
> files for every(?) package of the portage tree. But no report of bad
> digest.
Just for fun, I removed the files from the portage tree that were
reported as bad, and did another sync. Apparently, the rsync host
that got chosen that time had just been updated, be
el compilation
> take ~8h).
While that is not strictly enforced, I myself run an rsync server
locally, mostly to ensure that different systems have identical trees,
thus preserving my sanity.
Instructions for setting up a local rsync server can be found here:
https://wiki.gentoo.org/wiki/Pr
work with portage. And then the next logical
application is making your own /usr/local/portage not suck. Using git
as the main sync instead of rsync is something that's come about way
later, and really is fairly niche, compared to what the git capability
in portage was originally designed fo
Bill Kenworthy wrote:
> Rsync has a bwlimit argument which helps here. Note that rsync copies
> the whole file on what it considers local storage (which can be
> mounted network shares) ... this can cause a real slowdown.
> BillK
>
>
I ended up just letting it do its thing. I d
801 - 900 of 2788 matches
Mail list logo
