On 8/6/20 8:45 AM, J Martin Rushton via CentOS wrote:
C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
Is there a reason you think that? RHEL 7 was originally released with
3.0.9, so we can demonstrate that Red Hat will update not only revision,
but minor version increases within
On 7/29/20 6:28 PM, Johnny Hughes wrote:
> On 7/27/20 1:43 PM, Leon Fauster via CentOS wrote:
>> Am 27.07.20 um 19:50 schrieb Chris Schanzle via CentOS:
>>> Sorry if I'm being overly impatient, but is there some snag with
>>> releasing Thunderbird 68.10.0 for EL8?
>>>
>>> [RHSA-2020:3038-01]
FYI, the IUS rsync31u package is going to be retired (unmaintained) in
about a month. Upstream confirmed that there will never be another
3.1.x release.
https://github.com/WayneD/rsync/issues/80
https://github.com/iusrepo/announce/issues/23
If there is still value in providing a newer rsync
I have not built my own RPMs before, just built from source .tar.gz
files, do you have a good tutorial?
Is a package built by you inherently more secure than a package strait
from a mirror?
On 8/6/2020 8:12 PM, Chris Schanzle via CentOS wrote:
> On 8/6/20 12:30 PM, Jack Bailey via CentOS
On 8/6/20 12:30 PM, Jack Bailey via CentOS wrote:
> On 2020-08-06 08:45, J Martin Rushton via CentOS wrote:
>> You'll need to upgrade to CentOS8.
>>
>> C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
>>
>> C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
>>
>> Martin
>
> Another option is
I used that one, and it fixed the issue with the synology backup. 4 hrs
12 min into the backup and 1.5 TB backed up.
Thanks everyone!
On 8/6/2020 6:11 PM, John R. Dennison wrote:
> On Thu, Aug 06, 2020 at 10:40:14AM -0500, Christopher Wensink wrote:
>> Can anyone tell me the repository to use
On Thu, Aug 06, 2020 at 10:40:14AM -0500, Christopher Wensink wrote:
> Can anyone tell me the repository to use to upgrade to a version of
> rsync later than 3.1.2?
IUS has 3.1.3 for EL7. More information available via writeup at
https://wiki.centos.org/AdditionalResources/Repositories or
Am 06.08.20 um 21:10 schrieb Phil Perry:
On 06/08/2020 17:30, Jack Bailey via CentOS wrote:
On 2020-08-06 08:45, J Martin Rushton via CentOS wrote:
You'll need to upgrade to CentOS8.
C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
The problem that I keep running into is, our synology backup device
(RS3618xs) has an option to make a connection to each Linux VM, and our
file server's backup keeps failing every night with the error message:
"The samba shared folder settings of the source data cannot support
backup. Please
On 06/08/2020 17:30, Jack Bailey via CentOS wrote:
On 2020-08-06 08:45, J Martin Rushton via CentOS wrote:
You'll need to upgrade to CentOS8.
C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
Martin
Another option is to build rsync
Le 06/08/2020 à 16:53, Kenneth Porter a écrit :
> A practical equivalent is simply to avoid applying updates for a week to see
> if
> someone else gets burned by them. I'm already waiting for a weekend so I don't
> disrupt work in case a catastrophe happens, and I wait at least a week and
> watch
On 2020-08-06 08:45, J Martin Rushton via CentOS wrote:
You'll need to upgrade to CentOS8.
C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
Martin
Another option is to build rsync from source, which is what I did to try
out the zstd
You'll need to upgrade to CentOS8.
C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
Martin
On 06/08/2020 16:40, Christopher Wensink wrote:
Can anyone tell me the repository to use to upgrade to a version of
rsync later than 3.1.2?
Can anyone tell me the repository to use to upgrade to a version of
rsync later than 3.1.2?
Chris
--
Christopher Wensink
IS Administrator
Five Star Plastics, Inc
1339 Continental Drive
Eau Claire, WI 54701
Office: 715-831-1682
Mobile: 715-563-3112
Fax: 715-831-6075
On Thu, Aug 06, 2020 at 03:57:56PM +0200, Nicolas Kovacs wrote:
> Le 04/08/2020 à 08:31, lpeci a écrit :
> > I had the same problem with my UEFI bios machine and I fixed it so for
> > Centos 7:
While this worked for me, it might not work for you...
My "solution" was to boot the previous kernel,
On 8/6/2020 7:25 AM, Simon Matter via CentOS wrote:
The only real solution I can think of to prevent this would be to make
preview versions of updates available to the public so that a lot of
people can test them on their hardware, hopefully spare hardware, and give
feedback.
A practical
> Le 04/08/2020 à 08:31, lpeci a écrit :
>> I had the same problem with my UEFI bios machine and I fixed it so for
>> Centos 7:
>>
>> 1) Boot from an rescue linux usb
>>
>> 2) When the rescue system is running:
>>
>> 2.1) #chroot /mnt/sysimage
>>
>> 3) Config network:
>>
>> 3.1) # ip addr
Le 04/08/2020 à 08:31, lpeci a écrit :
> I had the same problem with my UEFI bios machine and I fixed it so for Centos
> 7:
>
> 1) Boot from an rescue linux usb
>
> 2) When the rescue system is running:
>
> 2.1) #chroot /mnt/sysimage
>
> 3) Config network:
>
> 3.1) # ip addr add
On 8/5/20 5:40 AM, Kenneth Porter wrote:
Is there some way we could get the initrd rebuild to be more verbose,
so that it doesn't appear to hang? It would be nice to get feedback
that something is happening, especially on an older, slower system
that takes a long time for this step.
While
Pete Biggs writes:
>
> > > man host
> > >
> > >-N ndots
> > >The number of dots that have to be in name for it to be
> > > considered absolute. The default value is that defined using
> > >the ndots statement in /etc/resolv.conf, or 1 if no ndots
> > > statement
> > man host
> >
> >-N ndots
> >The number of dots that have to be in name for it to be
> > considered absolute. The default value is that defined using
> >the ndots statement in /etc/resolv.conf, or 1 if no ndots
> > statement is present. Names with fewer dots
I also, don't see a search stanza.
Best Regards,
Strahil Nikolov
На 6 август 2020 г. 13:30:13 GMT+03:00, isdtor написа:
>Pete Biggs writes:
>> On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote:
>> > [root@localhost ~]# lsb_release -d
>> > Description: CentOS Linux release 8.2.2004 (Core)
Pete Biggs writes:
> On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote:
> > [root@localhost ~]# lsb_release -d
> > Description:CentOS Linux release 8.2.2004 (Core)
> > [root@localhost ~]# cat /etc/resolv.conf
> > # Generated by NetworkManager
> > search subdomain.company.com company.com
>
On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote:
> [root@localhost ~]# lsb_release -d
> Description: CentOS Linux release 8.2.2004 (Core)
> [root@localhost ~]# cat /etc/resolv.conf
> # Generated by NetworkManager
> search subdomain.company.com company.com
> nameserver 1.2.3.4
> nameserver
[root@localhost ~]# lsb_release -d
Description:CentOS Linux release 8.2.2004 (Core)
[root@localhost ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search subdomain.company.com company.com
nameserver 1.2.3.4
nameserver 5.6.7.8
[root@localhost ~]# host foo
foo.subdomain.company.com
25 matches
Mail list logo
