Re: [CentOS] OT: DELL PERC H200
If you want I will happily trade it for a perc 6 from a R610, the h200 is much better suited for zfs. Michael On Mar 21, 2014 11:22 PM, John R Pierce pie...@hogranch.com wrote: On 3/21/2014 2:52 PM, m.r...@5-cent.us wrote: Does anyone know if a PERC H200 is a real RAID controller? I'm about to build a box to CentOS 6.5 (it was Windows...) with RAID 6 on Monday, and this PE R610 has this I'm familiar with PERC 6 and 7s, but just dunno 'bout this one. if it doesn't have a flash-backed or battery-backed write-back cache, then it hardly matters what it is. the specs on that H200 sound like an LSI 2008 SAS2 HBA chip that has hardware mirroring, but without writeback cache. I'd configure it for JBOD and do my raid in the OS. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] USB thermometer - perl script - problem
Hopefully someone here could help. I need to debug, but I don't know much about perl. I bought a cheap USB thermometer: http://www.amazon.com/dp/B002VA813U?tag=grepular02-20 And found directions for use (for Linux) here: https://grepular.com/Using_Linux_to_Monitor_Room_Temperature_Remotely_and_Cheaply On a CentOS 6 machine, I have connected the USB device (it shows here as Microdia: [root@farm2 scripts]# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 006: ID 0c45:7401 Microdia With CPAN, I installed the Perl module Device::USB::PCSensor::HidTEMPer, as directed. That seemed to be successful. Now my perl script (as copied from grepular.com, see above) gives no error messages about missing modules. But I should get a temperature reading as output. Instead, I get no output at all. When I add to the script this: print $pcsensor; I get this as output: Device::USB::PCSensor::HidTEMPer=HASH(0x14d8900) But this: $pcsensor-list_devices(); gives no output. How could I debug this? - Jussi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] USB thermometer - perl script - problem
Do you find a temper-poll script in /usr/local/bin/ ? (I found that mentioned at https://github.com/padelt/temper-python ) This isn't really CentOS-specific. If you peruse further down the page you linked, one of the commenters describes the exact symptoms you're seeing, but they were running Ubuntu 12.04 LTS. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] sendmail delay in presenting banner
I am using a Centos 6.5 machine as a mail server with sendmail as the MTA. I have a problem with a delay of sendmail presenting its banner so that the process of accepting e-mail can begin. The log files demonstrate as much as a 2 minute delay between the connection and the banner presentation. #telnet Mail.DOMAIN.com 25 Connected to mail. Escape character is '^]'. two minute delay before the next line is presented h220 Mail.DOMAIN.com. ESMTP Sendmail 8.14.4/8.14.4; Sun, 23 Mar 2014 10:17:44 -0500 Log entries on the mail server for the above connection: Mar 23 10:16:05 Mail sendmail[31229]: NOQUEUE: connect from NAME.DOMAIN.com [10.0.0.187] Mar 23 10:17:44 Mail sendmail[31229]: AUTH: available mech=GSSAPI CRAM-MD5 DIGEST-MD5, allowed mech=EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN I have made the observation that if I put in the following line in the access file the 2 min delay goes away Connect:10.0.0.187 RELAY Obviously I can not set up a relay for every ip address, but this does solve the problem for internal network delivery of mail to the mail server. I am using named for local dns service and have not been able to identify any errors or problems. When I evaluate nslookup NAME.DOMAIN.com 127.0.0.1 I appropriately get 10.0.0.187 So far I am stumped on this problem, if any of you have suggestions I would appreciate your help Greg Ennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail delay in presenting banner
This is probably being caused by DNS timeout trying to reverse-lookup the connecting IP. Check that your resolver (/etc/resolv.conf) is set correctly and responding to e.g. dig -x [IP-address] queries in a timely manner. If you are using DHCP, note that /etc/resolv.conf may be automatically created by the network setup scripts so manual edits may not stick. On Sun, Mar 23, 2014 at 8:39 AM, Gregory P. Ennis po...@pomec.net wrote: I am using a Centos 6.5 machine as a mail server with sendmail as the MTA. I have a problem with a delay of sendmail presenting its banner so that the process of accepting e-mail can begin. The log files demonstrate as much as a 2 minute delay between the connection and the banner presentation. #telnet Mail.DOMAIN.com 25 Connected to mail. Escape character is '^]'. two minute delay before the next line is presented h220 Mail.DOMAIN.com. ESMTP Sendmail 8.14.4/8.14.4; Sun, 23 Mar 2014 10:17:44 -0500 Log entries on the mail server for the above connection: Mar 23 10:16:05 Mail sendmail[31229]: NOQUEUE: connect from NAME.DOMAIN.com [10.0.0.187] Mar 23 10:17:44 Mail sendmail[31229]: AUTH: available mech=GSSAPI CRAM-MD5 DIGEST-MD5, allowed mech=EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN I have made the observation that if I put in the following line in the access file the 2 min delay goes away Connect:10.0.0.187 RELAY Obviously I can not set up a relay for every ip address, but this does solve the problem for internal network delivery of mail to the mail server. I am using named for local dns service and have not been able to identify any errors or problems. When I evaluate nslookup NAME.DOMAIN.com 127.0.0.1 I appropriately get 10.0.0.187 So far I am stumped on this problem, if any of you have suggestions I would appreciate your help Greg Ennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail delay in presenting banner
This is probably being caused by DNS timeout trying to reverse-lookup the connecting IP. Check that your resolver (/etc/resolv.conf) is set correctly and responding to e.g. dig -x [IP-address] queries in a timely manner. If you are using DHCP, note that /etc/resolv.conf may be automatically created by the network setup scripts so manual edits may not stick. On Sun, Mar 23, 2014 at 8:39 AM, Gregory P. Ennis po...@pomec.net wrote: --- Bart, Thanks for your help. It smells like a DNS problem to me as well in particular I can fix the problem with a statement in the access file like Connect:10.0.0.186 RELAY When I checked reverse look up using 'dig -x [ip] I am not having any problems, and /etc/resolv.conf on the mail server is set where it is supposed to be 127.0.0.1 ; I have also tried pointing this to other dns servers, and I get the same problem. I have expanded the log file entry to : define(`confLOG_LEVEL', `29')dnl But this does not give me any more information other than there is a clear delay between the time of connecting and the time the sendmail banner is produced by the mail server. I am also not seeing any problem in the named.log file. Greg Ennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS} Does anyone use tcp_wrappers?
Most certainly YES!!! Next to iptables tcp_wrappers is a solid seconde line of defense. The argument that is is no longer developped is rubbish. The package does what is should do, functionality isexactly what it should be and it is bug free. Also it is flexible enough to do other tricks with it like spawning something depending on the ip address the incoming connection is coming from. It is a great product thanks to Wietse Venemaand others who integrated it to e.g. ssh. Dont drop it please!!! Adrian -- Adri P. van Bloois Antonlaan 104 email: adr...@pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax:NONE 52 05'15.77N 5 4'44.56E QTH-locater JO 22 OC When all is said and done, there is more said than done ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail delay in presenting banner
Date: Sun, 23 Mar 2014 10:39:34 -0500 I am using a Centos 6.5 machine as a mail server with sendmail as the MTA. I have a problem with a delay of sendmail presenting its banner so that the process of accepting e-mail can begin. The log files demonstrate as much as a 2 minute delay between the connection and the banner presentation. #telnet Mail.DOMAIN.com 25 Connected to mail. Escape character is '^]'. two minute delay before the next line is presented h220 Mail.DOMAIN.com. ESMTP Sendmail 8.14.4/8.14.4; Sun, 23 Mar 2014 10:17:44 -0500 Log entries on the mail server for the above connection: Mar 23 10:16:05 Mail sendmail[31229]: NOQUEUE: connect from NAME.DOMAIN.com [10.0.0.187] Mar 23 10:17:44 Mail sendmail[31229]: AUTH: available mech=GSSAPI CRAM-MD5 DIGEST-MD5, allowed mech=EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN I have made the observation that if I put in the following line in the access file the 2 min delay goes away Connect:10.0.0.187 RELAY Obviously I can not set up a relay for every ip address, but this does solve the problem for internal network delivery of mail to the mail server. I am using named for local dns service and have not been able to identify any errors or problems. When I evaluate nslookup NAME.DOMAIN.com 127.0.0.1 I appropriately get 10.0.0.187 So far I am stumped on this problem, if any of you have suggestions I would appreciate your help Greg Ennis --- Problem is solved a bit of an embarrassment ... I had two blacklisted services that were no longer active as a FEATURE in my sendmail.mc file. combined.njabl.org blackholes.mail-abuse.org Does anyone use other comparable services like these? Greg Ennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail delay in presenting banner
On 3/23/2014 11:49 AM, Gregory P. Ennis wrote: nslookup NAME.DOMAIN.com 127.0.0.1 I appropriately get 10.0.0.187 So far I am stumped on this problem, if any of you have suggestions I would appreciate your help in your DNS server, create a reverse zone for 10.0.0.0/8, like, 10.in-addr.arpa, even if it doesn't have any records other than NS and SOA. ideally, list all your local hosts on it. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS} Does anyone use tcp_wrappers?
On Sun, 2014-03-23 at 19:28 +0100, adr...@pa0rda.nl wrote: Most certainly YES!!! Next to iptables tcp_wrappers is a solid seconde line of defense. The argument that is is no longer developped is rubbish. Geen onzin :-) Who is developing the software's functionality ? There is no current maintainer. Inevitably software may need alterations, even small alterations, but without a volunteer maintainer how can those alterations be done uniformly to all versions all over the world ? No one has stated the software is bad. The comments have been its old and un-maintained. Old software does work well, so that is not an excuse to kill-it-off. But without a maintainer who can add new functions and repair any deficiencies (if they ever occur) what future has this software realistically got ? If TCP Wrappers disappears into oblivion after Centos/RHEL 7 finishes, is that likely to create a problem ? Individuals can, I assume, still compile it and use it with Centos. Mvg, -- Paul. England, EU. Our systems are exclusively Centos. No Micro$oft Windoze here. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS} Does anyone use tcp_wrappers?
On Sun, Mar 23, 2014 at 5:21 PM, Always Learning cen...@u62.u22.net wrote: There is no current maintainer. Inevitably software may need alterations, Inevitable - why? Bits don't just wear out. Don't break the interfaces it uses and software will just keep on working. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS} Does anyone use tcp_wrappers?
On Sun, Mar 23, 2014 at 5:21 PM, Always Learning cen...@u62.u22.net wrote: There is no current maintainer. Inevitably software may need alterations, On Sun, 2014-03-23 at 17:43 -0500, Les Mikesell wrote: Inevitable - why? Bits don't just wear out. Don't break the interfaces it uses and software will just keep on working. In my first two computer jobs characters had 9 bits; now characters have just 8. Bits do go missing :-) What is to stop a volunteer making a version for each Centos release ? and then putting it in a public repository ? The only difficulty I foresee is lack of modern (for RHEL/Centos 8) compilation libraries. I do not influence Red Hat's decisions. Perhaps it would help if a volunteer maintainer emerged as the new TCP Wrappers champion ? -- Paul. England, EU. Our systems are exclusively Centos. No Micro$oft Windoze here. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS} Does anyone use tcp_wrappers?
On 2014-03-23, Always Learning cen...@u62.u22.net wrote: I do not influence Red Hat's decisions. Perhaps it would help if a volunteer maintainer emerged as the new TCP Wrappers champion ? It certainly would, and therein lies the problem: nobody has actually volunteered for this position. From the original question posed, it seems like they would be more inclined to keep it if there were a maintainer. Because ultimately that's really the issue: it's not it doesn't work now but what happens if something breaks in the future? And please don't say what could break? because that would almost certainly jinx us, and we'd find a zero-day exploit within hours. ;-) I would like to observe that the original post did not state we are removing tcp wrappers from RHEL. It said we are discussing removing it from Fedora. And finally, if it did come to pass that tcp wrappers were removed from RHEL, a SIG or other group could emerge which could maintain packages for tcp wrappers for CentOS. (Yes, admins can compile their own packages, but that'd be something not directly CentOS-related.) --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
