Mój MacBook Pro z High Sierra pobrał wczoraj 13G podczas snu

9

System został prawdopodobnie zamknięty w moim miejscu pracy.

Jak mogę znaleźć dlaczego? Trochę światła na te 13 Gb? Jak Monitor aktywności znajduje te liczby? Z przyjemnością udzielę więcej informacji, gdy komputer nie zostanie jeszcze wyłączony. wprowadź opis zdjęcia tutaj

Nie mam automatycznych aktualizacji, ostatnia była 27 czerwca, ponad tydzień temu.

system.log jest pełen wpisów takich jak:

Aug  4 11:59:23 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Aug  4 11:59:33 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd[7132]): Service exited with abnormal code: 1
Aug  4 11:59:33 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Aug  4 11:59:44 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd[7133]): Service exited with abnormal code: 1
Aug  4 11:59:44 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Aug  4 11:59:54 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd[7134]): Service exited with abnormal code: 1
Aug  4 11:59:54 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Aug  4 12:00:04 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd[7135]): Service exited with abnormal code: 1
Aug  4 12:00:04 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Aug  4 12:00:14 MacBook-Pro-de-... com.apple.xpc.launchd[1] (com.apple.touristd[7136]): Service exited with abnormal code: 1

W nocy, kiedy powinien był spać - laptop był bardzo żywy:

Aug  4 00:53:44 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:53:51 MacBook-Pro syslogd[45]: ASL Sender Statistics
Aug  4 00:53:54 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3849]): Service exited with abnormal code: 1
Aug  4 00:53:54 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:54:04 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3850]): Service exited with abnormal code: 1
Aug  4 00:54:04 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:54:15 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3851]): Service exited with abnormal code: 1
Aug  4 00:54:15 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:54:26 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3852]): Service exited with abnormal code: 1
Aug  4 00:54:26 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 4 seconds. Pushing respawn out by 6 seconds.
Aug  4 00:54:36 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3853]): Service exited with abnormal code: 1
Aug  4 00:54:36 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:54:47 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3854]): Service exited with abnormal code: 1
Aug  4 00:54:47 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:54:57 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3855]): Service exited with abnormal code: 1
Aug  4 00:54:57 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:55:07 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3856]): Service exited with abnormal code: 1
Aug  4 00:55:07 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Aug  4 00:55:19 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd[3857]): Service exited with abnormal code: 1
Aug  4 00:55:19 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.touristd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.
Aug  4 00:55:28 MacBook-Pro systemstats[56]: assertion failed: 17A315i: systemstats + 641142 [8F334E9C-6F6C-3ED1-9251-D75E5C8E9EEC]: 0x5
Liviu
źródło
Czy masz włączoną automatyczną aktualizację dla dowolnego programu lub systemu?
Solar Mike
Nie, moi koledzy podejrzewają turystę czy coś takiego
Liviu
Na razie mamy ograniczone pasmo, więc jest to naprawdę ważne.
Liviu,
Touristd jest odpowiedzialny za „New to Mac?” powiadomienie, które pojawia się, gdy dopiero zaczynasz korzystać z komputera Mac. Sugeruję zainstalowanie Little Snitch obdev.at i stamtąd monitorowanie statystyk. Możesz zobaczyć, która aplikacja lub proces generuje tak dużo transferu danych.
l1ghthouse
@ Liviu Mogło być łatwiej blokować go całkowicie za pomocą Little Snitch
Skeleton Bow

Odpowiedzi:

4

To właśnie touristduruchamia się co kilka sekund i pobiera więcej niż 10 milionów na minutę. Nie wiem, co robi, próbowałem wyłączyć każdą opcję związaną z Internetem, ale ciągle się włączało.

$ launchctl unload /System/Library/LaunchAgents/com.apple.touristd.plist 
/System/Library/LaunchAgents/com.apple.touristd.plist: Operation not permitted while System Integrity Protection is engaged

Uruchom ponownie „Recovery OS”

csrutil enable --without fs --no-internal

Następnie uruchom ponownie normalnie i

$ sudo mkdir /backup
Password:
$ sudo mkdir /backup/System
$ sudo mkdir /backup/System/Library/
$ sudo mkdir /backup/System/Library/LaunchAgents/
$ sudo mv /System/Library/LaunchAgents/com.apple.touristd.plist /backup/System/Library/LaunchAgents/
$ ll /backup/System/Library/LaunchAgents/com.apple.touristd.plist 
-rw-r--r--  1 root  wheel  897 Mar 28 03:55 /backup/System/Library/LaunchAgents/com.apple.touristd.plist

Uruchom ponownie „Recovery OS”

csrutil enable
Liviu
źródło
To bolesne Doskonała analiza i kroki, aby wyłączyć sip i wyłączyć demona spthat. Zastanawiam się, czy muszę zgłosić błąd, aby uzyskać profil mamy, aby wyłączyć go w pracy. Wyraźnie warunek błędu i nie pobierze tych danych, gdy statek High Sierra zostanie wysłany.
bmike