climateprediction.net home page
System reinstallation makes cpdn require a new work unit

System reinstallation makes cpdn require a new work unit

Questions and Answers : Unix/Linux : System reinstallation makes cpdn require a new work unit
Message board moderation

To post messages, you must log in.

AuthorMessage
PRHumphrey

Send message
Joined: 28 Dec 04
Posts: 1
Credit: 260,426
RAC: 0
Message 9131 - Posted: 11 Feb 2005, 15:38:31 UTC

I have a dual-Opteron box running several flavours of Linux. The stable partition contains Gentoo AMD64, an experimental partition contains Gentoo ~AMD64 (a test and development version). Stable runs kernel 2.6.9-gentoo-r12 and test runs 2.6.10-gentoo-r7. The model code is in /usr/local, which is a separate partition mounted on whichever file system boots, and my user directory containing the working files is in /home, another partition mounted likewise. Thus there should be no need to restart cpdn from scratch whenever I reinstall the test system (which I do often), since the code is statically linked and simply copied into place.

But I find that on reinstalling Gentoo test, when I create my user and try to run the existing client in the existing working directory, the program restarts with CPU benchmarks. I then have to declare my cpdn identity and a new unit is fetched. But I usually find that I've now exceeded my daily quota, so the box sits idle for several hours.

What can I do to get around this awkwardness?

--
Rgds
Peter
ID: 9131 · Report as offensive     Reply Quote

Questions and Answers : Unix/Linux : System reinstallation makes cpdn require a new work unit

©2024 climateprediction.net