Questions and Answers :
Macintosh :
BOINC Manager engaging in spurious network activity
Message board moderation
Author | Message |
---|---|
Richard Cavell Send message Joined: 24 Apr 09 Posts: 4 Credit: 11,114 RAC: 0 ![]() |
Hi, I run BOINC 6.6.20 on a MacBook with OS 10.4.11. I exclusively run the SETI@Home project on my Core 2 Duo. Recently I have had problems with my MacBook paging to the swapfile at greater than 1 Hertz. I went into Activity Monitor to see what the problem is. Right now my network tab gives the following info: Packets in/sec: 12 Packets out/sec: 12 Data received/sec: 9.61 KB Data sent/sec: 9.61 KB The number of packets/sec is constant at 12. The data sent or received fluctuates occasionally, between 6 and 15. But as long as the BOINC manager is running, it's always there and never zero. However, BOINC *is not communicating with the server or attempting to do so*. I have reported all outstanding results. It happens even if I turn off Bluetooth, Airport, and unplug every cable from my computer. It happens even if I'm connected to the Internet without a firewall. The only thing that turns off the network activity is to quit the BOINC Manager. It really drains my computer's resources. It's one thing to hog my CPU, but quite another to engage in useless network activity. What is it doing? Richard |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
BOINC consists of multiple parts, but mostly of the client (daemon) and the GUI, which talk to each other through RCPs on TCP port 31416. Is it possible you see this? |
Richard Cavell Send message Joined: 24 Apr 09 Posts: 4 Credit: 11,114 RAC: 0 ![]() |
Yes, Jord, that's it, I think. It does seem to interfere with the performance of my TCP/IP stack. Still, I guess I don't run BOINC when I need performance. Richard |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
You can also Set up BOINC to run as a daemon, then you can quit the BOINC manager without stopping the client. They only talk to each other when both the GUI and the client are active, not when the GUI isn't running. |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.