garbage account password?

[Max Dettweiler]

Hi all,

I'm new to this project, and last night I grabbed my first k/n pair to test from the garbage account (I used the garbage account since its queue contains the lowest n-values). All has been going well so far, and I am at almost 20% through the test.

What I couldn't find anywhere on this forum, however, was what the password (for things such as expiring k/n pairs, etc.) for the garbage account was. Since it's a public account, shouldn't the password be posted publicly? Or is it already, and I just couldn't find it?

Thanks!

[vjs]

Max,

You are correct that the garbage account is a public account with no team or personal score.

I have run this account in the past as well, you can see what's going on there with the following....
http://www.seventeenorbust.com/stats...mhtml?userID=5

As far as passwords and management I'm pretty sure thats taken care of by the project creators. Currently it doesn't look like there are that many that need expiring etc.

[Max Dettweiler]

Max,

You are correct that the garbage account is a public account with no team or personal score.

I have run this account in the past as well, you can see what's going on there with the following....
http://www.seventeenorbust.com/stats...mhtml?userID=5

As far as passwords and management I'm pretty sure thats taken care of by the project creators. Currently it doesn't look like there are that many that need expiring etc.

Okay. Actually, the main reason why I was interested was so that I could go in and expire a test (since the Linux client apparently doesn't have the option to "when test completes, exit w/o new test"). Otherwise, there's no way to escape the "treadmill" of new tests being assigned once an old one finishes. (I don't plan to run SB all the time, just to intersperse it throughout work for other projects that I participate in, so this is important).

BTW, has anyone thought about including the "when test completes, exit w/o new test" option in the next version of SB for Linux? In the meantime, I guess my only option is to move the save file to a Windows virtual machine, apply the "fix for lost Proth test" thing, and finish the last bit of the test in the virtual machine (for which the SB client has the "exit w/o new test" option turned on).

Max

[Vato]

If you want to expire tests, just run this as your own username.
The complexity of the other stuff you mention, just isn't worth it IMHO.

[Max Dettweiler]

If you want to expire tests, just run this as your own username.
The complexity of the other stuff you mention, just isn't worth it IMHO.

Well, I could do that, except that I prefer the shorter tests in the garbage queue. (The garbage queue is handing out stuff in the 7M range right now, whereas secondpass is handing out 10M stuff.)

[Vato]

That's true, though by the very nature of the garbage account, you could be wasting your time since the tasks in that queue are just the oldest unreturned tasks, and could quite possibly be returned by the machine that was originally assigned them. And then again, you may well return a result that would otherwise become a dropped test after timeout. A bit of a lottery, but your machine, your choice. :-) Historically, I thought Louie ran garbage and discouraged others from doing so - doesn't look like that's still the case from the graphs.

(On an unrelated note, I'd sure like us to empty error-fix before doing second-pass, since we know at least one of the results returned is incorrect, and it'll help us to know our real error rate)