Displaying 6 results from an estimated 6 matches for "cormander".
Did you mean:
commander
2012 Mar 20
1
requesting edit perms for nagios
Hello,
My wiki username: cormander
URL requesting perms for:
http://wiki.centos.org/HowTos/Nagios
Thanks
2010 May 30
3
CentOS with Kernel 2.6.32 built-in
I have a Asus laptop, from the new generation, and my network driver is
present in the kernel since version 2.6.32(Jmicron). Is there any CentOS
with this kernel? I tried to compile myself, but I failed. Is a bit harder
than I thought.
Is there any testing version of CentOS or some backports?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2011 Nov 28
1
net-snmp-5.5-27.el6.i686
Hello,
Can someone explain why I don't get a timeout when I use the community string "public" even if I don't have it
defined in my snmpd.conf file. It doesn't return data but it also doesn't timeout. See example below.
...
rocommunity nobody 127.0.0.1
...
[root at L703108 pgsql]# snmpwalk -v 1 -c public 127.0.0.1 1.3.6.1.2.1.2.2.1 ifMIB
[root at L703108 pgsql]#
2012 Jan 06
1
rsyslog server cannot get the logs
I have an rsyslog server which is running Debian Stable,
and its version of rsyslog is 4.6.4-2.
All of my Debian Stable server can send log to it now.
and run both
nc $IP $PORT <<< "HELLO"
and
echo "HELLO" | nc $IP $PORT
on client, I can get log on the server.
While for my CentOS 5.7 server,
nc $IP $PORT <<< "HELLO"
works well, but
echo
2011 Dec 22
1
kernel panic/abort during boot
Just did an in-place update from 6.1 to 6.2 on my eeepc 901 (Atom CPU).
during boot, (if I hit ESC to see the boot messages) it says "starging udev"
then nothing else for a few seconds, then a huge register dump scrolls
by. it's too big to see the beginning of it.
If I boot from the prior kernel and look in /var/log/messages, I don't
see any evidence of the failed boot.
2011 Dec 15
3
Cause for kernel panic
Hi ! On an 8-node cluster, one of the node did a kernel panic.
The only bit of information I have is on a ssh console I had open, which
said :
Message from syslogd at node108 at Dec 14 19:00:15 ...
kernel:------------[ cut here ]------------
Message from syslogd at node108 at Dec 14 19:00:15 ...
kernel:invalid opcode: 0000 [#1] SMP
Message from syslogd at node108 at Dec 14 19:00:15 ...