NEEDED: people who can make the current linux client crash

I am using both Slackware-Current, 2.4.22, and Slackware 9.0 2.4.20, and none of the sb's work. All have segmentation fault within 1 minute of starting.

I also run Libranet 2.8.1, (Debian variant) and it runs great on sb102

just a shot in the dark but do you think it has anything to do with the version of either gcc or the version fo the kernel we are using?

Well I tried Suse8.2 this afternoon, and it did not work. then for haha's I loaded up a freebsd system to run the freebsd client, and while it runs, it will stop now and then. Another gent I know that uses freebsd said he has the same issue with the freebsd client stopping??

But so far the only linux distro I've got it running on is libranet 2.8.1 with sb102.

bump :( :sleepy:

Quote:

---

Originally posted by Brucifer
I am using both Slackware-Current, 2.4.22, and Slackware 9.0 2.4.20, and none of the sb's work. All have segmentation fault within 1 minute of starting.

I also run Libranet 2.8.1, (Debian variant) and it runs great on sb102

---

FWIW: I have sb100 running under Slack 9.0 2.4.20. I crashes or hangs between one and five times a day, but otherwise produces (apparently valid) output.

The only reason anybody on any OS is actually doing anything useful with the 17OB PRP client is the nice gentlemen who wrote wrapper/service programs that monitor the client and restart it when it goes down.

I'd like to add something odd I've noticed about my Linux client 1.02 on Red Hat 9. It's not crashing (unless you mean crashing the computer, too, which is occuring), but its block completion times are varying. I wouldn't have noticed it if it weren't for my proxy, but for at least a week blocks were completing at a steady 58min/blk (PII-400). Now, since a couple of days ago, they're taking up to 14 minutes longer, for no apparent reason, on the very same k and n. Top shows nothing conflicting.

It could be a hardware problem too (especially since the entire system is crashing sometimes), but I thought you might like to know.

status on a new client? I can't even run 1.0.2 on a P4 system I have, the other linux client I'm running on an athlon system dies nearly every day now.
Slack 9.1 /w 2.4.22

I'm anxious for a new Linux client as well. I haven't been able to complete a single block with SB 102 and RedHat 9 because of the Seg Faults. Please provide a status update.

Red Hat Linux 9.0 / Pentium 166 MMX (lol) / 128MB RAM
kernel 2.4.20-8 (redhat version of 2.4.20)

[keitsi@muuri keitsi]$ ./sb
Segmentation fault

sclient.log:
[Fri Dec 19 00:56:31 2003] client process [v1.0.2] invoked
[Fri Dec 19 00:56:31 2003] priority set to idle
[Fri Dec 19 00:56:31 2003] connecting to server

my email: keitsi at keitsi dot net

Quote:

---

Originally posted by kevinc
Good news!

Found the hint to use the IP address of sb.pns.net (216.163.34.105) in /etc/sclient.conf instead of the name. For whatever reason, that appears to get things running again.

Kevin C.

---

I tried that with Mandrake 9.2 using an AMD AthlonXP 2100+....It worked! Thanks! :cheers:

That still doesn't help me at all. :(

For the ip problem installing bind might fix that. I can't say for sure yet since I just started the client up but will post back as soon as it tries to connect

EDIT: ok that didn't work :p

I've tested 1.2.0 linux test version with Slackware9.1 kernel 2.4.24 on Duron 1800:

shrike@Srv2:~/SoB$ ./sb.120.test2 sclient.conf
[Mon Feb 16 11:17:48 2004] client process [v1.2.0] invoked
[Mon Feb 16 11:17:48 2004] priority set to idle
[Mon Feb 16 11:17:48 2004] connecting to server
Segmentation fault
shrike@Srv2:~/SoB$

Is it realy too difficult to make working client? Maybe you have to ask D.net guys how to?