Forum: DCypher.Net Support Forum
Topic: Linux Command line Crashing after Flush
Want to register?
Who Can Post? Any registered users may post a reply.
About Registration You must be registered in order to post a topic or reply in this forum.
Your UserName:
Your Password:   Forget your password?
Your Reply:


*HTML is ON
*UBB Code is ON
Options Show Signature: include your profile signature. Only registered users may have signatures.

If you have previously registered, but forgotten your password, click here.

*If HTML and/or UBB Code are enabled, this means you can use use HTML and/or UBB Code in your message.

Name Post
Colin Morey posted 02-03-2000 17:41 ET (US)
I'm currently running 2 copies of the GF project on a Dual p2-233 (replacement for a K6-2 450)

Running on RedHat 6.1.

I use the following script to start the two clients.

------------
#!/sbin/sh
cd ~/GFClient/
nohup ~/GFClient/gf_client > ~/client1 &
cd ~/GFClient2/
nohup ~/GFClient2/gf_client > ~/client2 &

------------

This starts both copies fine, and produces the logfile correctly.

I use this script to flush them

------------
#!/sbin/sh
cp ~user/commands ~user/GFClient/
cp ~user/commands ~user/GFClient2/
echo Flushing buffers
------------

which works fine, and if run on the same terminal as the previous script, shows both buffers being flushed. But, for some reason, when flushing the clients, they both crash, now, that's not a problem when on console, but I would like to have a setting in crontab to flush them automatically every hour or so.... I have set a large out-put buffer, so that if the link to the net dies, it will keep crunching for a while before dieing. it seems as if the linux version cannot over-run its buffers, unlike the windows client.

The short term answer is to append the 'run' script to the end of the flush script, but that is messy, and not something I really want to do. Any Ideas?

Colin Morey
Whizkid posted 02-15-2000 20:19 ET (US)
I have something that might be related.

I'm also running the GF Client under Redhat 6.1 (with an Athlon 500, not overclocked), and find it crashing at 100%. Here's a short log of what it does:


Completed 99.00% at a rate of 8836.76 Rays/s
Completed 100.00% at a rate of 8837.67 Rays/s
Segmentation fault (core dumped)
[whizkid@trollcave GFClient]$ ./gf_client
DCypher.net Gamma Flux Client for Linux v1.00
Copyright (c) 1999 of DCypher.net
Completed 96.00% at a rate of 7352.94 Rays/s
Completed 97.00% at a rate of 8038.59 Rays/s
Completed 98.00% at a rate of 8232.71 Rays/s
Completed 99.00% at a rate of 8410.43 Rays/s
Completed 100.00% at a rate of 170010.20 Rays/s
Sending block 1 to server
All blocks sent to server.  Closing connection
OutBuf Level: 0/1
Completed 1.00% at a rate of 8912.66 Rays/s


This is with the Athlon-optimized client. The same thing happened when I had a k6-2 using the "normal" linux x86 client.

When this happens I simply restart the client. Usually, it seems to stop crashing after one or two restarts tho (which seems a bit odd).

--Whizkid

[This message has been edited by Whizkid (edited February 15, 2000).]
Maciek posted 02-16-2000 08:05 ET (US)
I noticed the same with my PIII machines - it crushes at 100%, but only when there is no proxy to send results. So I was forced to write simple script checking if client is working. If no client exists it runs it again. Otherwise it occured sometimes that my clients were not working at night.

| Get 3DNow!

All submissions are copyrighted by their respective authors and are not for re-use in any form without their explicit written consent.

Powered by: Ultimate Bulletin Board, Version 5.37
© Madrona Park, Inc., 1998-1999.

Pentingnya Review Slot Online

Membaca review slot online bisa menjadi panduan yang sangat berguna. Review sering kali memberikan informasi tentang RTP slot tertinggi dan pengalaman pemain sebelumnya. Dengan memilih slot gacor yang telah direkomendasikan, peluang untuk menang dapat meningkat. Jadi, jangan lewatkan untuk memeriksa ulasan sebelum mulai bermain.

Related Links