Linux - GamesThis forum is for all discussion relating to gaming in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using PCLinuxOS 2007 and I think that I have discovered a bug in xboard/knights and wanted to know if anyone else has seen this. When running either xboard or knights with the GNUchess engine, GNUchess uses 100% of the CPU. Also when running knights, even after closing the program the GNUchess engine continues to run in the background, still using 100% of the CPU. Running GNUchess by itself from the command line does not show this condition.
this is not a bug the cpu calculates with full power as much moves as it can. If you use a multiprocessor optimized engine, you will see both cores at 100% while the engine is 'thinking'.
Quote:
Originally Posted by dmsynck
Running GNUchess by itself from the command line does not show this condition.
It has something to do with the way the engines are spawned.
Ideally the engines should be spawned like in a terminal (pty), so when you close the parent program, you are sure that the child process is closed as well.
Any non OS controlled ways, will lead to errors like this from time to time.
I've actually tried to use the pty way in some programs, but I tend to get some strange exitcodes: "15: ENOTBLK Block device required".
I don't understand there isn't a nicer way to do this in unix.
Yeah I noticed that. I started beating my laptop at chess and it began to heat up until the battery almost caught fire. I had to shut it down and fan the smoke.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.