HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- using obsolete setsockopt SO_BSDCOMPAT
Operating System - Linux
1830212
Members
1446
Online
109999
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2005 01:10 AM
10-14-2005 01:10 AM
using obsolete setsockopt SO_BSDCOMPAT
Hi, I've installed in a ProLiant DL360 the 'hpasm-7.3.0c-67.rhel4' package (RHEL 4).
During startup I get the following messages:
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
$uname -a
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
Any idea what could be the problem ?
Thanks in advance.
Jorge.-
During startup I get the following messages:
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
process `csginkgo' is using obsolete setsockopt SO_BSDCOMPAT
process `cmathreshd' is using obsolete setsockopt SO_BSDCOMPAT
$uname -a
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
Any idea what could be the problem ?
Thanks in advance.
Jorge.-
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2006 05:41 AM
01-13-2006 05:41 AM
Re: using obsolete setsockopt SO_BSDCOMPAT
I am seeing the same problem.
Do we have a fix? I understand that above processes are using the deprecated setsocketopt SO_BSDCOMPAT.
Do we have a fix? I understand that above processes are using the deprecated setsocketopt SO_BSDCOMPAT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2006 02:53 AM
01-17-2006 02:53 AM
Re: using obsolete setsockopt SO_BSDCOMPAT
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.
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.
HP knows this, so the developers of the hpasm package probably aren't in a big hurry to fix that.
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.
HP knows this, so the developers of the hpasm package probably aren't in a big hurry to fix that.
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP