climateprediction.net home page
TS logging

TS logging

Questions and Answers : Unix/Linux : TS logging
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile astroWX
Volunteer moderator

Send message
Joined: 5 Aug 04
Posts: 1496
Credit: 93,520,069
RAC: 25,565
Message 96 - Posted: 5 Aug 2004, 19:26:49 UTC

We seem to be back to logging every TS on the Console Log. Accident or purposeful? (Makes for a lot of scrolling!)

BTW, I\'ve looked for the log on HD but not found it. Or does it scroll into the bit-bucket? (Easier to find logs in the old SuSE 7.1 than in 9.)
________________________________________________
Washing one's hands of the conflict between the powerful and the powerless means to side with the powerful, not to be neutral.
-- Paulo Freire (1921-1997), educator, author.
ID: 96 · Report as offensive     Reply Quote
old_user1
Avatar

Send message
Joined: 5 Aug 04
Posts: 907
Credit: 299,864
RAC: 0
Message 138 - Posted: 6 Aug 2004, 4:38:35 UTC

I moved back to monitoring every second since there were some major changes David A. did to the BOINC client in which I can get a signal on a suspend/quit etc (i.e. major changes we needed to run CPDN under BOINC smoothly). So I get 5 seconds to try and clean things up before BOINC really kills everything, hence having to monitor in less time. It's a quick process and the hadsm3_* (monitor program) still shows far less CPU time than the model (I have it at a minute on mine, most of which is for unzipping and showing graphics; versus 10 hours for the model).

I actually don't log quite as much as the old Windows CPDN as I want to keep hard drive activity low; so there should be the restart dump write every 144 timesteps (checkpoint) and hopefully that's it!

ID: 138 · Report as offensive     Reply Quote
Profile astroWX
Volunteer moderator

Send message
Joined: 5 Aug 04
Posts: 1496
Credit: 93,520,069
RAC: 25,565
Message 142 - Posted: 6 Aug 2004, 4:46:29 UTC - in response to Message 138.  

> I moved back to monitoring every second since there were some major changes
> David A. did to the BOINC client in which I can get a signal on a suspend/quit
> etc (i.e. major changes we needed to run CPDN under BOINC smoothly). So I get
> 5 seconds to try and clean things up before BOINC really kills everything,
> hence having to monitor in less time. It's a quick process and the hadsm3_*
> (monitor program) still shows far less CPU time than the model (I have it at a
> minute on mine, most of which is for unzipping and showing graphics; versus 10
> hours for the model).
>
> I actually don't log quite as much as the old Windows CPDN as I want to keep
> hard drive activity low; so there should be the restart dump write every 144
> timesteps (checkpoint) and hopefully that's it!
>

Thanks, Carl. Makes sense -- and explanations ALWAYS welcome.
Jim
________________________________________________
Washing one's hands of the conflict between the powerful and the powerless means to side with the powerful, not to be neutral.
-- Paulo Freire (1921-1997), educator, author.
ID: 142 · Report as offensive     Reply Quote

Questions and Answers : Unix/Linux : TS logging

©2019 climateprediction.net