LHC@home

What are you doing with a V5 VBOX?!! It's up to 6.1 now.
I would suggest updating and trying to get Atlas tasks again.
You are seriously out of date.

And go through Yeti's checklist to double check everything.

The currently active monitoring script doesn't output anything at ALT-F2 until at least 1 event has finished.
As the current ATLAS batch sometimes needs up to 30-40m per event it may look like ALT-F2 has crashed.

Be patient.
I already sent David a suggestion for an improved monitoring but there are a few (hopefully minor) issues to solve before it can go live.

.....There is an increase of load with the current ATLAS simulation campaign, so we will add another file server to increase capacity.

the 24hrs is the time to return the WU, so if you can run 1 at a time them you could have a buffer of 16-24WU's and still be fine.

If you had n CPU's then you could do n times this.

Since Atlas doesn't really use BOINC's task managment the most WU's you can have at anytime is 24 anyway.

In theory the 0.5 work buffer would store an additional 8-12WU's, so you could exceed the 24hr limit.

The max of 24 is only irritating to people with more than 24 cores, as they have more cores that the allowed WU limits, a better server setting would be to only allow 24WU/core/day