LLRnet server rally port 300 May 3rd-4th

[Lennart]

Originally Posted by Anonymous

Wow, 20 cores! I say keep it up!

Ok I have now 30 core on the server and have to stay there becuse i cant take the other 13 quad off sieving.

/Lennart

[mdettweiler]

Originally Posted by Lennart

Ok I have now 30 core on the server and have to stay there becuse i cant take the other 13 quad off sieving.

/Lennart

No problem--30 cores in and of itself is still a HUGE help!

[mdettweiler]

I just noticed that there is a user called "linux" returning results to the LLRnet server. That sounds like it could be part of some sort of internal naming system--does anyone know if this is a mistake or not? (If necessary, AES can merge it with the user's correct name after the rally--he's done that in the past with other people.)

[Lennart]

Originally Posted by Anonymous

I just noticed that there is a user called "linux" returning results to the LLRnet server. That sounds like it could be part of some sort of internal naming system--does anyone know if this is a mistake or not? (If necessary, AES can merge it with the user's correct name after the rally--he's done that in the past with other people.)

It was me!! Forget to set my call on one It shall be sm5ymt

/lennart

[mdettweiler]

Originally Posted by Lennart

It was me!! Forget to set my call on one It shall be sm5ymt

/lennart

Okay, no problem, I'm sure AES can fix it up for you once the rally's over and things have "settled down" a bit.

[mdettweiler]

I just noticed that two users, one named "AMDUsers_Brucifer" and the other named just "Brucifer" showed up in the LLRnet stats--I'm assuming that the latter was an error since it doesn't have the team name in it. I've added both to the AMD Users team for the time being; after the rally Adam can merge the stats for "Brucifer" into "AMDUsers_Brucifer".

[Brucifer]

Originally Posted by Anonymous

I just noticed that two users, one named "AMDUsers_Brucifer" and the other named just "Brucifer" showed up in the LLRnet stats--I'm assuming that the latter was an error since it doesn't have the team name in it. I've added both to the AMD Users team for the time being; after the rally Adam can merge the stats for "Brucifer" into "AMDUsers_Brucifer".

yeah, I was experimenting. They should both be under AMDUsers_Brucifer. :)

Having an issue though on 64-bit linux systems. Is the linux llrnet client statically compiled or not? Runs okay on 32-bit linux, except slackware v12.0 which is 32-bit. So it's a library issue, as earlier 32-slack systems run it fine. Any comments?

[mdettweiler]

Originally Posted by Brucifer

yeah, I was experimenting. They should both be under AMDUsers_Brucifer. :)

Having an issue though on 64-bit linux systems. Is the linux llrnet client statically compiled or not? Runs okay on 32-bit linux, except slackware v12.0 which is 32-bit. So it's a library issue, as earlier 32-slack systems run it fine. Any comments?

I think it's dynamically linked, though if you want to try compiling it as a statically linked application you can get the source code here. (Instructions for compiling are included. It's actually pretty easy--I've done it a couple times myself--though I imagine it would be a little more complicated if you wanted to have it statically linked.)

Edit: Oh, forgot to ask, what exactly is the problem you're having on Slackware 12.0? Does it just not even start at all? Or does it have problems connecting to the server? If it's the latter then that's a known issue with DNS resolution that shows up on certain Linux distros--a recompile should fix it. (Last I heard, the affected distros were Debian and Redhat based distros--which includes me since I'm on Ubuntu--though I vaguely remember someone mentioning problems on Slackware. If you want I can send you my compiled version, compiled on a Ubuntu system running 7.10 at the time.)

[gd_barnes]

I am thrilled at all of the new people joining the rally!

Welcome Lennart and Brucifer to the effort!


Gary

[Brucifer]

Originally Posted by Anonymous

Edit: Oh, forgot to ask, what exactly is the problem you're having on Slackware 12.0? Does it just not even start at all? Or does it have problems connecting to the server? If it's the latter then that's a known issue with DNS resolution that shows up on certain Linux distros--a recompile should fix it. (Last I heard, the affected distros were Debian and Redhat based distros--which includes me since I'm on Ubuntu--though I vaguely remember someone mentioning problems on Slackware. If you want I can send you my compiled version, compiled on a Ubuntu system running 7.10 at the time.)

yep, boils down to resolution, it's happening for me on mepis-64, opensuse 10.2, 10.2, 10.3, and slack 12.0. Something with the way they are handling the "localhost" issue within. Slack 10.x and earlier aren't having any issues.

You have an url for your recompiled version where I could suck it down?

Also, is this server setup going to be good after this push is over Sunday?

[gd_barnes]

Adam,

We have some serious firepower on this rally! Your server seems to be handling the load very well. Let us know if you encounter any issues.


Gary