<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic using obsolete setsockopt SO_BSDCOMPAT in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649637#M20133</link>
    <description>Hi, I've installed in a ProLiant DL360 the 'hpasm-7.3.0c-67.rhel4' package (RHEL 4).&lt;BR /&gt;&lt;BR /&gt;During startup I get the following messages:&lt;BR /&gt;&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;&lt;BR /&gt;$uname -a&lt;BR /&gt;Linux baslxmr001.corp.mycompany.net 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 i686 i386 GNU/Linux&lt;BR /&gt;&lt;BR /&gt;Any idea what could be the problem ?&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;Jorge.-</description>
    <pubDate>Fri, 14 Oct 2005 08:10:14 GMT</pubDate>
    <dc:creator>Jorge Carminati</dc:creator>
    <dc:date>2005-10-14T08:10:14Z</dc:date>
    <item>
      <title>using obsolete setsockopt SO_BSDCOMPAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649637#M20133</link>
      <description>Hi, I've installed in a ProLiant DL360 the 'hpasm-7.3.0c-67.rhel4' package (RHEL 4).&lt;BR /&gt;&lt;BR /&gt;During startup I get the following messages:&lt;BR /&gt;&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT&lt;BR /&gt;&lt;BR /&gt;$uname -a&lt;BR /&gt;Linux baslxmr001.corp.mycompany.net 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 i686 i386 GNU/Linux&lt;BR /&gt;&lt;BR /&gt;Any idea what could be the problem ?&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;Jorge.-</description>
      <pubDate>Fri, 14 Oct 2005 08:10:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649637#M20133</guid>
      <dc:creator>Jorge Carminati</dc:creator>
      <dc:date>2005-10-14T08:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: using obsolete setsockopt SO_BSDCOMPAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649638#M20134</link>
      <description>I am seeing the same problem. &lt;BR /&gt;Do we have a fix? I understand that above processes are using the deprecated setsocketopt SO_BSDCOMPAT.</description>
      <pubDate>Fri, 13 Jan 2006 13:41:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649638#M20134</guid>
      <dc:creator>shrey_1</dc:creator>
      <dc:date>2006-01-13T13:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: using obsolete setsockopt SO_BSDCOMPAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649639#M20135</link>
      <description>For now, it is just a warning: when you see those messages, you know that you should not upgrade your kernel to Linux-2.7.xx (or greater) kernel series. That series is likely to drop the support of (some of) the things that are now working-but-obsolete.&lt;BR /&gt;&lt;BR /&gt;Because RHEL4 seems to be frozen on kernel version 2.6.9 + an increasing amount of backported patches (the -22 in the kernel version number), this is unlikely to cause you any problems while you stay with standard RHEL 4.&lt;BR /&gt;&lt;BR /&gt;HP knows this, so the developers of the hpasm package probably aren't in a big hurry to fix that.</description>
      <pubDate>Tue, 17 Jan 2006 10:53:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-obsolete-setsockopt-so-bsdcompat/m-p/3649639#M20135</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2006-01-17T10:53:13Z</dc:date>
    </item>
  </channel>
</rss>

