When there are no major crises all I can do is report on the more mundane details of my day. So here goes:

We're still waiting on some minor tweaks before splitting multibeam data and sending it out. The ball isn't in my court at this point. In the meantime I debugged and tested my splitter automation scripts so we can hit the ground running when we are ready. Also dusted off some other scripts and am working on populating the "credited job" table which I talked about many weeks ago. Helped Jeff install an OS on yet another new server recently donated by Intel. The single server will probably be the new setiathome.berkeley.edu web server as this single machine is about 5 times as powerful as our current two current web servers (kosh and klaatu) combined. Intel has been very good to us lately. Jeff and I had another good chat about the nitpicker design as well. On top of all that, I noticed one of the routers in our current ISP configuration was blocking some administrative traffic. This didn't affect the public servers at all, but still it needed to be fixed. Editing router configs makes me nervous as one false move and you blocked everything including your current login and any future logins. Luckily there's always "reload in 5." If only real life worked that way. This particular router is in our server closet, so I could always just power cycle it in a pinch - unlike other routers on our network which are far, far away.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Thanks Matt for the update!

Thanks Intel for the server!!

Can you take alook at the top computers page - something seems to be worong there form the 2nd page onwards. The sorting switches from RAC to Total Credit and back...

mic.

---

mic.

Great news Matt!! And ditto on the thanks to Intel, very awesome! Its always good to hear no bad news. :-) Keep up the great work guys. :-)

Jeremy

---

Mundane News is Good News.
Thanks to you and Intel.

All right Intel...

and Oh, may the Seti Gods have many mundane days to come...

... Editing router configs makes me nervous as one false move and you blocked everything including your current login and any future logins. ... other routers on our network which are far, far away.

Yep, very easily done. However, you only tend to do that sort of trick just once...

I rather like this config option in shorewall:

#
# FOR ADMINS THAT REPEATEDLY SHOOT THEMSELVES IN THE FOOT
#
# Normally, when a "shorewall stop" command is issued or an error occurs during
# the execution of another shorewall command, Shorewall puts the firewall into
# a state where only traffic to/from the hosts listed in
# /etc/shorewall/routestopped is accepted.
#
# When performing remote administration on a Shorewall firewall, it is
# therefore recommended that the IP address of the computer being used for
# administration be added to the firewall's /etc/shorewall/routestopped file.
#
# Some administrators have a hard time remembering to do this with the result
# that they get to drive across town in the middle of the night to restart
# a remote firewall (or worse, they have to get someone out of bed to drive
# across town to restart a very remote firewall).
#
# For those administrators, we offer ADMINISABSENTMINDED=Yes. With this setting,
# when the firewall enters the 'stopped' state:
#
# All traffic that is part of or related to established connections is still
# allowed and all OUTPUT traffic is allowed. This is in addition to traffic
# to and from hosts listed in /etc/shorewall/routestopped.
#
# If this variable is not set or it is set to the null value then
# ADMINISABSENTMINDED=No is assumed.
#

ADMINISABSENTMINDED=Yes

And very good that Intel are being kindly with a donating a new server. I would guess s@h must boost their sales somewhat! (And AMD's)

I hope Francoise "Who?" can put in a good word for a Penryn or few, thanks Intel ;-)


Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

When there are no major crises all I can do is report on the more mundane details of my day. So here goes:

We're still waiting on some minor tweaks before splitting multibeam data and sending it out. The ball isn't in my court at this point. In the meantime I debugged and tested my splitter automation scripts so we can hit the ground running when we are ready. Also dusted off some other scripts and am working on populating the "credited job" table which I talked about many weeks ago. Helped Jeff install an OS on yet another new server recently donated by Intel. The single server will probably be the new setiathome.berkeley.edu web server as this single machine is about 5 times as powerful as our current two current web servers (kosh and klaatu) combined. Intel has been very good to us lately. Jeff and I had another good chat about the nitpicker design as well. On top of all that, I noticed one of the routers in our current ISP configuration was blocking some administrative traffic. This didn't affect the public servers at all, but still it needed to be fixed. Editing router configs makes me nervous as one false move and you blocked everything including your current login and any future logins. Luckily there's always "reload in 5." If only real life worked that way. This particular router is in our server closet, so I could always just power cycle it in a pinch - unlike other routers on our network which are far, far away.

- Matt

Matt,

Do you have a view on the v5.10.7 BOINC client and the ability to abort queued WU's where a quorum has been reached? FWIW I like the feature (keeps my queue populated with valid scientific work) but it will impact on the rate at which split work is consumed by the userbase. The 'Client Connection Statistics' are offline at present, but the %age of clients deployed will be low initially.

---

Thanks for the information.

Has anyone approached HP for possible equiptent or help?

Ed Michau