When I logged online this morning, my rc5 window came up and said there was an error connecting - it slept for 3 secs - then instead of Virus' "Burrb - Ah that hit the spot" there was instead something to effect of "moo moo moo" or some such.. then dumped the packets.
I checked my Keyserver hostname and it still reads 188.8.131.52 and now the readings are correct with the "Burrb..." message.
What happened? I hope those packets didn't go somewhere else..
Mod w/ an attitude
I just checked my distributed.net keyserver and is it set for:
both are valid key servers but you should use the one that Socalgal has if you want the stats to show on Virus stat page. both keyservers will credit the blocks to what ever "team" you are on. (should be SYSOPT though!) Socal, I would say that there must have been a glitch in the system as you connected to one of Dnet's servers instead of virus as his still say "Burb..Ahh"
What happened was that you were probably doing a lot of network transfering or something to that effect, but it let up while attempting to access the d.net keyserver (the backup), and the blocks went straight to distributed.net instead of going through Virus's pproxy. The blocks will still be credited at distributed.net, but they won't show on Virus's pproxy stats.
It's really no big deal as long as you're aware of it. I usually try to keep an eye on the connects I make to ensure they go to the pproxy, then minimize it again once it starts. I've had a few thousand blocks skip the pproxy, and since this bugged me a little, I keep an eye on the beginning of any major (200+) transfers. [img]/forum/smile.gif[/img]
Will Sysopt still get credit if we have the server set as default?
Well, I have shut down and restarted a few times during the day, indeed it must have been some glitch, as "Burrb.." is coming up consistently. I will be keeping an eye on it though.
They'll still get credited. They just won't have anything to do with your stats on the pproxy, should you desire those stats to appear.
i may be mistaken but that sounds like the default keyserver but should still be credited to the team just not on virus's page
My cable connection is still not very stable. And sometimes, it might lose connection for a minute or two.
If you are using the GUI client. You can turn on Never Fallback which will prevent it from using a d.net keyserver when it can't find the sysopt pporxy. As for the CLI version. I think setting 'Keyserver is a personal proxy on a protected LAN' to yes. Will work, but I haven't tested it fully.
I KNEW there had to be a reason for NEVER FALL BACK.
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke