Reply to thread

Message

<blockquote data-quote="Csmac" data-source="post: 1665673" data-attributes="member: 273394">In trying to reduce Internet data usage on a MBP with Yosemite 10.10.3 we found that a process named nsurlsessiond with a user of nsurlsessiond was downloading like crazy. the computer had been doing nothing except sitting there when the thread started. Since we have a 4G Internet connection it grabbed a bunch of data really quickly. The download was stopped by turning off the WiFi at which time we tracked down the process via Process Monitor. My question is how to find out what started this unrequested, at least by the user, download. In looking at another MBP with the same OSx level, I found two of the same threads that were not doing anything. I just need to be able to track down what started the download so it can be turned off. At this point all we can do is to kill the thread, but I'm sure it will restart probably on the next logon or reboot.<img src="/mac_images/images/smilies/Angry.png"&nbsp; class="smilie" loading="lazy" alt=":Angry:" title="Angry&nbsp; &nbsp; :Angry:" data-shortname=":Angry:" />The computer has been gone over and everything we can think of has been turned off for updates, but obviously something is trying.Ideas? All are welcome and thanks.Cliff</blockquote>

[QUOTE="Csmac, post: 1665673, member: 273394"] In trying to reduce Internet data usage on a MBP with Yosemite 10.10.3 we found that a process named nsurlsessiond with a user of nsurlsessiond was downloading like crazy. the computer had been doing nothing except sitting there when the thread started. Since we have a 4G Internet connection it grabbed a bunch of data really quickly. The download was stopped by turning off the WiFi at which time we tracked down the process via Process Monitor. My question is how to find out what started this unrequested, at least by the user, download. In looking at another MBP with the same OSx level, I found two of the same threads that were not doing anything. I just need to be able to track down what started the download so it can be turned off. At this point all we can do is to kill the thread, but I'm sure it will restart probably on the next logon or reboot.:Angry: The computer has been gone over and everything we can think of has been turned off for updates, but obviously something is trying. Ideas? All are welcome and thanks. Cliff [/QUOTE]

Verification

Name this item. 🍎