http://predictor.scripps.edu/forum_thread.php?id=1913

BURP has caused Seti, Predictor, LHC, and Einstein on my main computer to send back errors for the past 2 days - the time BURP started sending out work units.

I detatched from BURP and I will never attatch to that trashy project again!

---

-----

I detatched from BURP and I will never attatch to that trashy project again!

OH NO, NOT ANOTHER FRUSTRATION JUNKIE! Phah!

BURP obviously have a bug to sort out in that case. Have you checked to see if it is a known bug? Have you POLITELY communicated the problem to the devs?

You're welcome to detach as I assume you have done.

INSULTS AGAINST THE PROJECT ARE NOT APPROPRIATE.

See various other threads here to see some of the mess caused by whatever childish insults...

Also, your title for this thread could and should be much better worded.


Good luck,
Martin

---

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

Oh please, I'm one of the original cheerleaders here when 99% of the people in SetiBoinc were calling for blood when there weren't enough work units to go around.

This isn't just a bug - it's a bug that pulls down EVERY project. If it was a self-contained problem, it wouldn't matter. But this affects EVERYTHING, and I can't trust a project that will render my entire computer impotent.

And the title of this thread is fine.

---

-----

This isn't just a bug - it's a bug that pulls down EVERY project. If it was a self-contained problem, it wouldn't matter. But this affects EVERYTHING, and I can't trust a project that will render my entire computer impotent.

Its obviously 'unexpected'.

And if it is affecting all other Boinc projects, then both Boinc and Burp need debugging on that one.

And if your computer is also being rendered (sorry, bad Burp pun) useless, then you've got hardware problems or you need your OS configuring better or another OS.


For security and resilience, I run Boinc under its own unprivileged user on a Linux system. Any 'unexpected damage' would trash that user only and leave the rest of the system fully usable.

Sorry, but for my UK English, I think your use of "screw" is somewhat overemotive...


Good luck,
Martin

---

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

screw up
Slang: To make a mess of (an undertaking).

---

-----

From the BURP front page:

Currently this is a pre-alpha project...

That implies that it is unstable and will very likely cause unexpected side-effects up to and including making your computer unbootable. You were warned so I don't quite understand your bad feelings towards the project now.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

Don't pull this "holier-than-thou" junk. Read the title of the thread: WARNING

I am warning other people who run BURP. Geez.

The part about me never attaching again is just my 2 cents ^_^

---

-----

Why post it here in the Number Crunching forums on Seti@Home?

Why not post it in the BURP forums? I checked, you didn't post one iota about it there. So you have me wondering.

And we can do without the name calling and flame-baiting.

---

Yes, we can do without the insults. Please stop getting on my case!

I posted it here because this is a busy, populated forum. I can warn many people here!

Geez, no good deed goes unpunished. I'm through with this thread.

---

-----

... Geez, no good deed goes unpunished. I'm through with this thread.

Good for the warning. Sorry, but with the emotive words you used, I read a bad insulting frustrated tone to the post.

Rephrasing, the heat could have been avoided with:

Warning: BURP halts all other projects!

BURP has caused Seti, Predictor, LHC, and Einstein on my main computer to send back errors for the past 2 days - the time BURP started sending out work units.

I detatched from BURP and the problems vanished!

BURP is still very pre-Apha!

Usefully informative, no mud slinging and no insults.

Thanks,
Martin

---

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

BURP is pre-alpha... Use at your own risk...

This glitch has been known for quite some time, and it has been mentioned (more than once I believe) that BURP does not yet play well with others, so it isn't advisable to run other projects alongside.

But yes, by all means, never attach to that 'trashy' project again. More work for everyone else. :)

Matt

If you had read the forums over at burp, You would have known about potential problems and how to avoid them.

Burp is co-existing with other projects on my system without any problems other than those already known about. Also Janus has stated over there that a fix is in but was not part of this phase of the pre-alpha testing of the blender client.

1) you plan a project and come to some conclusion about how to set it up
2) you start in pre-alpha stage to get things moving
3) once most is working according to plan it is alpha
4) then beta phase starts to find anything that may have been overlooked
5) when all is as expected it becomes general use for everyone

Note we are a long way from step 5 and I left out alot to simplify the explaination of the phases of a project.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

Don't pull this "holier-than-thou" junk. Read the title of the thread: WARNING

I am warning other people who run BURP. Geez.

The part about me never attaching again is just my 2 cents ^_^

It would of been a lot smarter to:

A) post this at the BURP forum
B) not dis BURP
C) find out if others have had problems

and for your info. BURP works 100% for me (other than 2 errors possibly caused by CPDN having an error causing an error OR they both had something on my PC that caused an error.

BoB

---

Do you Good Search for Seti@Home? http://www.goodsearch.com/?charityid=888957
Or Good Shop? http://www.goodshop.com/?charityid=888957

[font='courier,courier new']All this time I thought "dis" was written with two Ss...

I agree - Confirm before blasting a project. (Once you've confirmed the error, then you can blast disses)

Do your logs show any errors? Are you running a Wintel box or some tricked-out HW? Don't pussy-out on us: Give us some fing info.[/font]

---

It's a known Bug with BURP that it can take over some of your other Projects. I've had it happen to me several times already. Pirates when it was running at times would do the same thing.

Nobody at the BURP site knows for sure the reason for it taking over Projects other than maybe it isn't shutting down fast enough and the next project to run gets shoved into the Slot with the BURP Blender and then BURP takes over that Project.

Just to be safe I only run BURP with the rest of my Projects Suspended so they don't run at the same time, once BURP runs out of WU's for that Session I start up the other Projects again.

---

It's a known Bug with BURP that it can take over some of your other Projects. I've had it happen to me several times already. Pirates when it was running at times would do the same thing.

Nobody at the BURP site knows for sure the reason for it taking over Projects other than maybe it isn't shutting down fast enough and the next project to run gets shoved into the Slot with the BURP Blender and then BURP takes over that Project.

Just to be safe I only run BURP with the rest of my Projects Suspended so they don't run at the same time, once BURP runs out of WU's for that Session I start up the other Projects again.

Blender is not sutting down fast enough in some cases. I had one copy of blender.exe that was still running 3 weeks after the last round of BURP. I reported the problem before the current round was released, and the current round was sent without a fix. This indicates a fairly cavalier attitude.

---

BOINC WIKI

Blender is not sutting down fast enough in some cases. I had one copy of blender.exe that was still running 3 weeks after the last round of BURP. I reported the problem before the current round was released, and the current round was sent without a fix. This indicates a fairly cavalier attitude.

Or the problem is subtle and difficult to trace, or that the problem is known but difficult to fix...

Do you know any more of the story?

Magic is for fairy tales. I'm sure you appreciate the debug process.

Cheers,
Martin

---

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

Blender is not sutting down fast enough in some cases. I had one copy of blender.exe that was still running 3 weeks after the last round of BURP. I reported the problem before the current round was released, and the current round was sent without a fix. This indicates a fairly cavalier attitude.

Or the problem is subtle and difficult to trace, or that the problem is known but difficult to fix...

Do you know any more of the story?

Magic is for fairy tales. I'm sure you appreciate the debug process.

Cheers,
Martin

I appreciate the debug process very well - I make my living writing software. I also understand what a showstopper is.

---

BOINC WIKI

Blender is not sutting down fast enough in some cases. I had one copy of blender.exe that was still running 3 weeks after the last round of BURP. I reported the problem before the current round was released, and the current round was sent without a fix. This indicates a fairly cavalier attitude.
==========

John, I was running the Burp Project pretty heavy yesterday and when I finally ran out of WU's from there I made a casual check of some of the Slots on my PC's and I remembered seeing the Blender Exe in one of them yet. At the time I just thought it was kinda funny it was still there but didn't do anything about it.

Well I just did a full check of all my PC's & sure enough it was still there mixed in with a LHC WU. I also checked the Task Manager and the Blender Exe was still running too. So far it hadn't taken over anything yet but it probably would have. To be safe I just deleted the entire slot since I only had a few minutes on that LHC WU anyway.