similar to: rsync via floppy

I just took a look at the 2.5.5 codebase to see how easy it would be to write a little driver script that downloads a big directory tree from an rsync daemon the chunky way (get a list of a module's subdirectories and do the transfer by subdirectory). The reason for doing this is obvious when you have large directory trees, as is the case for many of us. Unfortunately the way list_only is

I am puzzled as to why I can't get the option --link-dest to work properly. When I use this option when both source and destinations are on a local filesystem the hard-linking of the target against the link-dest directory does work, but when the source is a remote directory (via ssh or rsync server) hard links are not created. I suspect it has something to do with setting the correct

Wayne, I have been using the rsync snapshot from 1/25 for the last few days and everything seems quite solid so far. I include below a few nit-picks in case you're looking for thing to tidy up. I'm also looking forward to hearing news about the --filter option. I'm thinking it is going to be very useful for backup purposes. What I would want to be able to do is, on a

Dear all, I've been trying to track down a problem with timeouts when pulling data from an rsync daemon and I have now run out of any useful ideas. The problem manifests itself when I try to transfer a large directory tree on a slow client machine. What happens then is that the client rsync process successfully receives the list of files from the server, then begins checking the local

Chris, to put things in the right prespective, you should read (if you haven't done so already) the original paper describing the design behind batch mode. The design and implementation of this functionality goes back to a project called the Internet2 Distributed Storage Infrastructure (I2-DSI). As part of that project, the authors created a modified version of rsync (called rsync+)

I, too, was disappointed with rsync's performance when no changes were required (23 minutes to verify that a system of about 3200 files was identical). I wrote a little client/server python app which does the verification, and then hands rsync the list of files to update. This reduced the optimal case compare time to under 30 seconds. Here's what it does, and forgive me if these sound

On Tue, Sep 24, 2019 at 12:08 PM Phelps, Matthew <mphelps at cfa.harvard.edu> wrote: > > I *know* there has been a lot going on, and congratulations on getting > CentOS 8 out! > > But(!), I don't see any updates to CO 7.7.1908 in the "updates" directory > on the mirrors I typically use. All the files date from Sept. 14th. > > Is something broken? >

I *know* there has been a lot going on, and congratulations on getting CentOS 8 out! But(!), I don't see any updates to CO 7.7.1908 in the "updates" directory on the mirrors I typically use. All the files date from Sept. 14th. Is something broken? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical

This is not your usual "so when is CO 7.8.xxxx coming out?" posts. I'm just curious if the CentOS team is affected by our current world conditions, or is work-from-home modus operandi for the team? (In other words, "when is CO 7.8.xxxx coming out?") -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian

Forgive me if this has been answered before and I've missed it. This https://access.redhat.com/solutions/2206511 says live kernel patches will be available via yum updates as of RHEL 7.7. Is this carried over to CentOS 7.7.1908? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical Observatory) Center for

On Thu, Feb 28, 2019 at 11:52 AM mark <m.roth at 5-cent.us> wrote: > Nicolas Kovacs wrote: > > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : > > > >> I want to lock in the SDA/SDB/SDC for my drives > > > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > > >

On Fri, Dec 14, 2018 at 10:04 AM isdtor <isdtor at gmail.com> wrote: > > > > So the syntax looks to be > > > > > > repo --name=epel --baseurl=nfs://server:/path > > > > > > that colon after server is not a spelling error. > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48 > > > > That seems to work

On Fri, Oct 4, 2019 at 9:24 AM Stephen John Smoogen <smooge at gmail.com> wrote: > On Fri, 4 Oct 2019 at 08:18, Phelps, Matthew <mphelps at cfa.harvard.edu> > wrote: > > > > On Fri, Oct 4, 2019 at 6:33 AM Jim Perrin <jperrin at centos.org> wrote: > > > > > > > > > > > On 10/3/19 9:35 PM, Stephen John Smoogen wrote: > >

On Fri, Apr 3, 2020 at 4:09 PM Patrick DERWAEL <patrick at derwael.be> wrote: > Exactly the same... ??? > > > [root at plexvm ~]# mount -t cifs //192.168.1.200/mp3 /home/plex/Musique > --verbose -o username=plex,password=plex,domain=DERWAEL,ro,auto,vers=3.0 > mount.cifs kernel mount options: > >

On Fri, Oct 4, 2019 at 6:26 AM Jim Perrin <jperrin at centos.org> wrote: > > > On 10/3/19 2:42 PM, Jerry Geis wrote: > > I have need to use the old network-scripts and not NetworkManager. > > Why? I'd like to understand more about the use case where this is a > requirement. > > > One example we have is qemu virtual machine hosts where setting up the

I learned from the Centos-devel email list that they aren't sending out email to centos-announce for updates to CentOS 8, but only updating an RSS feed. I think this is a bad idea since no one uses RSS anymore (ducks for cover). What do others here think of this? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical

On Fri, Oct 4, 2019 at 6:33 AM Jim Perrin <jperrin at centos.org> wrote: > > > On 10/3/19 9:35 PM, Stephen John Smoogen wrote: > > On Thu, 3 Oct 2019 at 13:52, Phelps, Matthew <mphelps at cfa.harvard.edu> > wrote: > >> > >> On Thu, Oct 3, 2019 at 1:42 PM Jim Perrin <jperrin at centos.org> wrote: > >> > >>> >

On Thu, Oct 3, 2019 at 1:42 PM Jim Perrin <jperrin at centos.org> wrote: > > > On 10/3/19 1:32 PM, Phelps, Matthew wrote: > > Forgive me if this has been answered before and I've missed it. > > > > This https://access.redhat.com/solutions/2206511 says live kernel > patches > > will be available via yum updates as of RHEL 7.7. Is this carried over to

On Thu, Oct 10, 2019 at 9:04 AM Nux! <nux at li.nux.ro> wrote: > There was a recent thread about Redhat's removal of drivers from LSI > SAS2, it's probably the problem you are facing. > It can be worked around with the help of Elrepo repo. > > > https://lists.centos.org/pipermail/centos/2019-October/173682.html > > >

Rsync list: Alberto and I have done a couple more exchanges by private email, and we found that he wasn't turning on my include/exclude optimization in his test because he had an "exclude" directive in rsyncd.conf. He has now removed that and run the test again. His very interesting results are below with my comments. Note that his case is rather pathological because he's got