On Mar 22, 2017, at 7:56 PM, James Pifer wrote:
> In a nutshell I've tried the following commands, in many different ways and
> orders, but when the system restarts it still seems to end up with some form
> of default rules. It even has a couple rules specifying
I apologize if this has been asked and answered, but I googled and
attempted things for several hours today without success.
I have a freshly installed CentOS 7 system that I'd like to disable the
firewall and all iptables rules. Basically the equivalent of doing
iptables -F
In a nutshell
On 03/22/2017 03:26 PM, Matt Garman wrote:
> Is anyone on the list using kerberized-nfs on any kind of scale?
Not for a good many years.
Are you using v3 or v4 NFS?
Also, you can probably stuff the rpc.gss* and idmapd services into
verbose mode, which may give you a better ideas as to whats
On 22/03/17 05:31 PM, Johnny Hughes wrote:
> On 03/22/2017 08:27 AM, Phelps, Matthew wrote:
>> On Wed, Mar 22, 2017 at 9:16 AM, Valeri Galtsev
>> wrote:
>>
>>>
>>> On Wed, March 22, 2017 7:46 am, Phelps, Matthew wrote:
Red Hat released RHEL 6.9 yesterday.
On 03/22/2017 08:27 AM, Phelps, Matthew wrote:
> On Wed, Mar 22, 2017 at 9:16 AM, Valeri Galtsev
> wrote:
>
>>
>> On Wed, March 22, 2017 7:46 am, Phelps, Matthew wrote:
>>> Red Hat released RHEL 6.9 yesterday.
>>>
>>> Why isn't CentOS 6.9 out yet? :)
>>>
>> Somebody
Feel free to contact me offline if you wish. I'll just go on record as saying
that it's a bear
- On 22 Mar, 2017, at 12:26, Matt Garman matthew.gar...@gmail.com wrote:
| Is anyone on the list using kerberized-nfs on any kind of scale?
|
| I've been fighting with this for years. In
Y cuando tuve uno problema de seguridad fue por permitir el RALAY al
localhost. Una vez eliminado esto se resolvieron muchos problemas.
Saludos,
David
El día 22 de marzo de 2017, 17:49, David González Romero
escribió:
>> Uno de los dolores de cabeza mas grandes en mi
> Uno de los dolores de cabeza mas grandes en mi proceso como Sysadmin de
> Postfix es que no existe la forma de limitar el numero de relays permitidos
> por usuario, vaya, que por ejemplo "micue...@micorreo.com" solo pueda sacar
> un maximo de 1,000 (un mil) correos diarios, de esta forma
Matt Garman wrote:
> Is anyone on the list using kerberized-nfs on any kind of scale?
>
We use it here. I don't think I'm an expert - my manager is - but let me
think about your issues.
> Just to give a little insight into our issues: we have an
> in-house-developed compute job dispatching
Is anyone on the list using kerberized-nfs on any kind of scale?
I've been fighting with this for years. In general, when we have
issues with this system, they are random and/or not repeatable. I've
had very little luck with community support. I hope I don't offend by
saying that! Rather, my
James B. Byrne wrote:
> Looking at transaction 367 more closely we see that the kernel was
> updated to 2.6.32-642.15.1.el6.x86_64 on March 10 but that a number or
> errors, whose nature I do not comprehend, were also reported.
>
> # yum history info 367
> Loaded plugins: etckeeper,
Hi Patrick,
I did not disabled on grub or module because of Centos 7 FAQ tips
"Upstream employee Daniel Walsh recommends not disabling the ipv6 module, as
that can cause issues with SELinux and other components, but adding the
following to /etc/sysctl.conf"
So I used only sysctl, but the
Thanks!
Eliezer
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Gordon Messmer
Sent: Monday, September 21, 2015 9:46 PM
To: CentOS
I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8.
This instance is used for occasional development projects which
require segregation. Thus it is seldom accessed.
At some point in the recent past this guest developed an issue with
starting. Specifically these messages were
Listo el programa que escuchaba por el puerto no estaba activo,
Slds,
El 22 de marzo de 2017, 10:09, Wilmer Arambula escribió:
> Gracias por tu respuesta si efectivamente ya habia hecho lo que me
> comentastes, de hech he podido abrir puertos sin problemas usando
I actually move the default *.repo files and replace them with "".
The thing is that Katello turns all the downloaded yum content into a
single redhat.repo file and I don't have to install any more *-release-*
rpms any more.
I would argue that I should not need to install any *-release-*
On Wed, Mar 22, 2017 at 9:16 AM, Valeri Galtsev
wrote:
>
> On Wed, March 22, 2017 7:46 am, Phelps, Matthew wrote:
> > Red Hat released RHEL 6.9 yesterday.
> >
> > Why isn't CentOS 6.9 out yet? :)
> >
> Somebody has to do a hard work, I'm sure. Thanks, guys for the
On Wed, March 22, 2017 7:46 am, Phelps, Matthew wrote:
> Red Hat released RHEL 6.9 yesterday.
>
> Why isn't CentOS 6.9 out yet? :)
>
Somebody has to do a hard work, I'm sure. Thanks, guys for the great work
you are doing!
Or you as sysadmin know that and just being ironic?
Valeri
>
>
> --
>
Y tu selinux esta activo?
Estoy seguro que selinux esta bloqueando lo que quieres hacer.
PD: firewalld e iptables son distintos. pero puedes deshabilitar firewalld
he instalar iptables
Saludos
*Pablo Flores AravenaIngeniero Informátic*o
Sysadmin, Centro de Tecnología de la Información
Wilmer
Tienes una confusion, firewalld e iptables son servicios de seguridad
diferentes y es mas, no deben convivir juntos.
Debes parar y hacer un mask del servicio iptables para que firewalld
funcione correctamente.
Este link puede orientarte
https://www.unixmen.com/iptables-vs-firewalld/
Buenos dias estoy tratando de abrir un rango de puertos por Firewalld
(Iptables) pero no logro abrirlos:
Comando:
sudo firewall-cmd --permanent --zone=external --add-port=35500-36000/tcp
sudo firewall-cmd --permanent --zone=external --add-port=35500-36000/udp
sudo firewall-cmd -reload
Sudo
Red Hat released RHEL 6.9 yesterday.
Why isn't CentOS 6.9 out yet? :)
--
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
The last few lines are
NMI watchdog: disabled CPU0 hardware events not enabled
NMI watchdog: shutting down hard lockup detector on all CPUS
installing Xen timer for CPU1
installing Xen timer for CPU2
installing Xen timer for CPU3
installing Xen timer for CPU4
installing Xen timer for CPU5
On 21-03-17 20:51, Diaulas Castro wrote:
Used steps on sysctl from Centos7 FAQ (https://wiki.centos.org/FAQ/CentOS7) and
some gathered on internet
# cat /etc/sysctl.d/90-disable_ipv6.conf
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.eth0.disable_ipv6=1
24 matches
Mail list logo