- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: linkloop & RHEL5
Operating System - Linux
1753412
Members
7524
Online
108793
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО09-15-2010 05:42 AM
тАО09-15-2010 05:42 AM
HI,
I'm trying to implement linkloop in a RHEL5.4 box.
I have GLIBC 2.5, but in the README it says only support up to 2.4, is there any option to make it run properly.
When I executed, I got this:
# uname -a
Linux phpnag01.inf.sta 2.6.18-164.el5PAE #1 SMP Tue Aug 18 15:59:11 EDT 2009 i686 i686 i386 GNU/Linux
# linkloop -i bond0 00:23:7D:D8:ED:CC
Link connectivity to LAN station: 00:23:7D:D8:ED:CC (HW addr 0x00237DD8EDCC)
*** buffer overflow detected ***: linkloop terminated
======= Backtrace: =========
/lib/libc.so.6(__chk_fail+0x41)[0x67c1c1]
/lib/libc.so.6[0x67b7cc]
linkloop[0x80489ad]
linkloop[0x804935f]
/lib/libc.so.6(__libc_start_main+0xdc)[0x5abe9c]
linkloop[0x8048851]
======= Memory map: ========
004e3000-004ee000 r-xp 00000000 fd:00 296569 /lib/libgcc_s-4.1.2-20080825.so.1
004ee000-004ef000 rwxp 0000a000 fd:00 296569 /lib/libgcc_s-4.1.2-20080825.so.1
00578000-00592000 r-xp 00000000 fd:00 296562 /lib/ld-2.5.so
00592000-00593000 r-xp 00019000 fd:00 296562 /lib/ld-2.5.so
00593000-00594000 rwxp 0001a000 fd:00 296562 /lib/ld-2.5.so
00596000-006d5000 r-xp 00000000 fd:00 296563 /lib/libc-2.5.so
006d5000-006d6000 --xp 0013f000 fd:00 296563 /lib/libc-2.5.so
006d6000-006d8000 r-xp 0013f000 fd:00 296563 /lib/libc-2.5.so
006d8000-006d9000 rwxp 00141000 fd:00 296563 /lib/libc-2.5.so
006d9000-006dc000 rwxp 006d9000 00:00 0
00a3b000-00a3c000 r-xp 00a3b000 00:00 0 [vdso]
08048000-0804a000 r-xp 00000000 fd:00 1400509 /usr/bin/linkloop
0804a000-0804b000 rw-p 00001000 fd:00 1400509 /usr/bin/linkloop
0863e000-0865f000 rw-p 0863e000 00:00 0 [heap]
b7f18000-b7f19000 rw-p b7f18000 00:00 0
b7f22000-b7f24000 rw-p b7f22000 00:00 0
bf892000-bf8a7000 rw-p bffea000 00:00 0 [stack]
Aborted
# ll /lib/libc.so.6
lrwxrwxrwx 1 root root 11 May 9 2009 /lib/libc.so.6 -> libc-2.5.so
I'm trying to implement linkloop in a RHEL5.4 box.
I have GLIBC 2.5, but in the README it says only support up to 2.4, is there any option to make it run properly.
When I executed, I got this:
# uname -a
Linux phpnag01.inf.sta 2.6.18-164.el5PAE #1 SMP Tue Aug 18 15:59:11 EDT 2009 i686 i686 i386 GNU/Linux
# linkloop -i bond0 00:23:7D:D8:ED:CC
Link connectivity to LAN station: 00:23:7D:D8:ED:CC (HW addr 0x00237DD8EDCC)
*** buffer overflow detected ***: linkloop terminated
======= Backtrace: =========
/lib/libc.so.6(__chk_fail+0x41)[0x67c1c1]
/lib/libc.so.6[0x67b7cc]
linkloop[0x80489ad]
linkloop[0x804935f]
/lib/libc.so.6(__libc_start_main+0xdc)[0x5abe9c]
linkloop[0x8048851]
======= Memory map: ========
004e3000-004ee000 r-xp 00000000 fd:00 296569 /lib/libgcc_s-4.1.2-20080825.so.1
004ee000-004ef000 rwxp 0000a000 fd:00 296569 /lib/libgcc_s-4.1.2-20080825.so.1
00578000-00592000 r-xp 00000000 fd:00 296562 /lib/ld-2.5.so
00592000-00593000 r-xp 00019000 fd:00 296562 /lib/ld-2.5.so
00593000-00594000 rwxp 0001a000 fd:00 296562 /lib/ld-2.5.so
00596000-006d5000 r-xp 00000000 fd:00 296563 /lib/libc-2.5.so
006d5000-006d6000 --xp 0013f000 fd:00 296563 /lib/libc-2.5.so
006d6000-006d8000 r-xp 0013f000 fd:00 296563 /lib/libc-2.5.so
006d8000-006d9000 rwxp 00141000 fd:00 296563 /lib/libc-2.5.so
006d9000-006dc000 rwxp 006d9000 00:00 0
00a3b000-00a3c000 r-xp 00a3b000 00:00 0 [vdso]
08048000-0804a000 r-xp 00000000 fd:00 1400509 /usr/bin/linkloop
0804a000-0804b000 rw-p 00001000 fd:00 1400509 /usr/bin/linkloop
0863e000-0865f000 rw-p 0863e000 00:00 0 [heap]
b7f18000-b7f19000 rw-p b7f18000 00:00 0
b7f22000-b7f24000 rw-p b7f22000 00:00 0
bf892000-bf8a7000 rw-p bffea000 00:00 0 [stack]
Aborted
# ll /lib/libc.so.6
lrwxrwxrwx 1 root root 11 May 9 2009 /lib/libc.so.6 -> libc-2.5.so
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2010 06:44 AM
тАО09-15-2010 06:44 AM
Solution
I'd guess you have found an old linkloop binary RPM and installed it.
Get the source code from Sourceforge:
http://sourceforge.net/projects/linkloop/
Recompile it on RHEL 5.4 (gcc, binutils and glibc-devel packages required to compile successfully):
$ tar zxvf linkloop-1.0.1-hp.tar.gz
$ ./configure
$ make
Once you recompile it, it will be linked against GLIBC 2.5 of RHEL 5.x, so it will work again.
You may install the linkloop binaries to /usr/local/bin by running "make install" as root, but then they won't be managed by the RPM package management system. A better way would be to create your own RPM package: it's more work, but it allows you to easily distribute the package to multiple systems, and to easily upgrade/remove it if/when necessary.
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
MK
Get the source code from Sourceforge:
http://sourceforge.net/projects/linkloop/
Recompile it on RHEL 5.4 (gcc, binutils and glibc-devel packages required to compile successfully):
$ tar zxvf linkloop-1.0.1-hp.tar.gz
$ ./configure
$ make
Once you recompile it, it will be linked against GLIBC 2.5 of RHEL 5.x, so it will work again.
You may install the linkloop binaries to /usr/local/bin by running "make install" as root, but then they won't be managed by the RPM package management system. A better way would be to create your own RPM package: it's more work, but it allows you to easily distribute the package to multiple systems, and to easily upgrade/remove it if/when necessary.
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2010 01:52 AM
тАО09-17-2010 01:52 AM
Re: linkloop & RHEL5
thks!
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP