> Am 16.12.2018 um 00:07 schrieb Gordon Messmer :
>
> On 12/15/18 1:05 PM, Frank Cox wrote:
>> Ultimately it would be very useful to have some kind of a tool that would
>> generate a report from the rpms installed on a system and tell you exactly
>> what depends on what else. Among other thin
On 12/17/18 3:50 AM, Leon Fauster via CentOS wrote:
or this one :-)
rpm -ev --test PACKAGENAME
will list all packages that require PACKAGENAME
True. I considered that, and then decided that I could never recommend
using "rpm -e" as a test, even with the --test flag, due to the risk of
oper
> On 12/17/18 3:50 AM, Leon Fauster via CentOS wrote:
>>
>> or this one :-)
>> rpm -ev --test PACKAGENAME
>> will list all packages that require PACKAGENAME
>
>
> True. I considered that, and then decided that I could never recommend
> using "rpm -e" as a test, even with the --test flag, due to th
hi guys,
I updated to qemu-kvm-common-ev-2.12.0-18.el7_6.1.1.x86_64 (also
libvirt) and my Centos 6.10 kvm guests now do not start.
Funnily enough Win10 guest are fine, only Centoses cannot start,
silently & without any errors.
Any care to comment?
many thanks, L.
_
On Mon, Dec 17, 2018 at 01:30:14PM +0800, yf chu wrote:
> I am a website developer. We deploy a Nginx server on centos to provide HTTP
> services. Recently, some customers of our website were complaining about that
> occasionally they could not open the webpage, the web browser show that the
>
On Mon, Dec 17, 2018 at 05:50:44PM +, lejeczek via CentOS wrote:
> I updated to qemu-kvm-common-ev-2.12.0-18.el7_6.1.1.x86_64 (also libvirt)
> and my Centos 6.10 kvm guests now do not start.
>
> Funnily enough Win10 guest are fine, only Centoses cannot start, silently &
> without any errors.
>
On Mon, Dec 17, 2018 at 01:52:40PM -0500, Jonathan Billings wrote:
>
> On Mon, Dec 17, 2018 at 05:50:44PM +, lejeczek via CentOS wrote:
> > I updated to qemu-kvm-common-ev-2.12.0-18.el7_6.1.1.x86_64 (also libvirt)
> > and my Centos 6.10 kvm guests now do not start.
> >
> > Funnily enough Win10
On Sat, Dec 15, 2018 at 11:11 PM Kaushal Shriyan
wrote:
> Hi,
>
> Is there a way to find out how the CentOS 7.5 Linux box got infected with
> malware?
> Currently i am referring to
> http://sudhakarbellamkonda.blogspot.com/2018/11/blocking-watchbog-malwareransomware.html
> to carry out the below
On Tue, Dec 18, 2018 at 01:02:23AM +0530, Kaushal Shriyan wrote:
> Checking in again if anyone can pitch in for my earlier email to this
> mailing list. Thanks in Advance.
Wipe your system and reload it from clean backups. Change all your
passwords and SSH keys. Check every other host you've eve
On 17/12/2018 17:24, Simon Matter wrote:
On 12/17/18 3:50 AM, Leon Fauster via CentOS wrote:
or this one :-)
rpm -ev --test PACKAGENAME
will list all packages that require PACKAGENAME
True. I considered that, and then decided that I could never recommend
using "rpm -e" as a test, even with
On Sat, Dec 15, 2018 at 12:40 PM Kaushal Shriyan
wrote:
>
> Hi,
>
> Is there a way to find out how the CentOS 7.5 Linux box got infected with
> malware?
> Currently i am referring to
> http://sudhakarbellamkonda.blogspot.com/2018/11/blocking-watchbog-malwareransomware.html
> to carry out the below
On 12/17/18 2:57 PM, Mauricio Tavares wrote:
On Sat, Dec 15, 2018 at 12:40 PM Kaushal Shriyan
wrote:
Hi,
Is there a way to find out how the CentOS 7.5 Linux box got infected with
malware?
Currently i am referring to
http://sudhakarbellamkonda.blogspot.com/2018/11/blocking-watchbog-malwarer
> Is there a way to find out how the CentOS 7.5 Linux box got infected with
> malware?
> Currently i am referring to
> http://sudhakarbellamkonda.blogspot.com/2018/11/blocking-watchbog-malwareransomware.html
> to carry out the below steps and is done manually.
>
> 1)rm -fr /tmp/*timesyncc.servic
On 17 December 2018 9:58:03 p.m. "Pete Biggs" wrote:
Is there a way to find out how the CentOS 7.5 Linux box got infected with
malware?
Currently i am referring to
http://sudhakarbellamkonda.blogspot.com/2018/11/blocking-watchbog-malwareransomware.html
to carry out the below steps and is do
I have used tcpdump to capture the data packets and found that after the ssl
handshake, the client side reset the tcp connection.
Is there any method to pinpoint the culprit who drops the tcp connection?
At 2018-12-18 01:58:36, "Fred Smith" wrote:
>On Mon, Dec 17, 2018 at 01:30:14PM +0800
Hi,
My mail server is running on CentOS 7 with Postfix, Dovecot and
Spamassassin. I get quite a lot of spam on a few accounts, and
Spamassassin does its job fine. Spam mail is identified correctly, and
it looks like there are no false positives, e. g. valid mail is never
identified as spam.
When
16 matches
Mail list logo
