| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 33
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@ SekeRob.
I did that edit to the file, I rebooted the rig & even pulled the etho cable before I started Boinc up and it did not change a thing as soon as I plugged the cable back in Boinc started polling my router again as soon as the manager was up, no tasks running. I have no idea what's going on here, never had this happen before, only thing to try now is to wipe Boinc out & try an install of the 7.0.65 I got in .deb files without any network connection up when I do it to see if that make a difference, I'm out of ideas otherwise. thanks |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's not polling the router... it's passing through the NIC, -never- leaving the computer, and only when the BM is loaded, not when the BM GUI is not running, which you confirmed. This is how it's designed [see Lawrence post]. Long as you're seeing "Connected to localhost (7.0.27), you're fine. Opposed, if WIFI -fails- to connect to the router, it starts to suck so much resource that tasks start crashing with heartbeat issues / signal 11. If there were router connection need when the BM is up, then something would get logged in the messages/event file stdoudae.txt.
Before I thought you were seeing it on the router, but now with the ethernet cable pulled, that's all the confirmation needed... You're seeing NIC signal of 127.0.0.1 ... 1) which never leaves the comp, 2) which some firewalls are passing back as flicker in the systray bar, 3) which can be disabled or exempted FAIK (did not know GUFW did that, the one I use). not able to think of anything else. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hurrah!
![]() |
||
|
|
|