Last edit: @sgardner in <!error getting other user for D3CP17MBP> 2 years ago - Slack Archive

If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports -mindepth 1 -delete > /dev/null 2>&1```

History

If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports -mindepth 1 -delete > /dev/null 2>&1```
If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports -mindepth 1 -delete```
If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete```
If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports/ -name "suggestd*.crash" -delete -o -name "followupd*.crash" -delete```
If your iTerm is running slow, it's because `~/Library/Logs/DiagnosticReports` has been spammed by constantly crashing services. To prevent those services from running and clear their logs, add the following to your `~/.zshrc`:
```launchctl remove com.apple.suggestd
launchctl remove com.apple.followupd
find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete```
If your iTerm is running slow, run `cd ~/Library/Logs/DiagnosticReports; open .`
If you see logs named `suggestd_*.crash`, delete the faulty symlink with `rm ~/Library/Suggestions`
If you see logs named `followupd_*.crash`, disable the faulty service with `launchctl remove com.apple.followupd`
For any other errors, pray that the crash logs are not empty, open them to see what the issue is, and google a way to fix it.
Afterwards, clear the logs from the folder with `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` :fiestaparrot:
If your iTerm is running slow, run `cd ~/Library/Logs/DiagnosticReports; open .`
If you see logs named `suggestd_*.crash`, delete the faulty symlink with `rm ~/Library/Suggestions`
If you see logs named `followupd_*.crash`, disable the faulty service with `launchctl remove com.apple.followupd`
For any other errors, pray that the crash logs are not empty, open them to see what the issue is, and google a way to fix it.
Afterwards, clear the logs from the folder with `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` :upside_down_face:
If your iTerm is running slow, run `cd ~/Library/Logs/DiagnosticReports; open .`
If you see logs named `suggestd_*.crash`, delete the faulty symlink with `rm ~/Library/Suggestions`.
If you see logs named `followupd_*.crash`, disable the faulty service with `launchctl remove com.apple.followupd`
For any other errors, pray that the crash logs are not empty, open them to see what the issue is, and google a way to fix it.
Afterwards, clear the logs from the folder with `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` :upside_down_face:
If your iTerm is running slow, run `cd ~/Library/Logs/DiagnosticReports; open .` If you see logs named `suggestd_*.crash`, delete the faulty symlink with `rm ~/Library/Suggestions`. If you see logs named `followupd_*.crash`, disable the faulty service with `launchctl remove com.apple.followupd` For any other errors, pray that the crash logs are not empty, open them to see what the issue is, and google a way to fix it. Afterwards, clear the logs from the folder with `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` :upside_down_face:
If your iTerm is running slow, run `cd ~/Library/Logs/DiagnosticReports; open .` If you see logs named `suggestd_*.crash`, delete the faulty symlink with `rm ~/Library/Suggestions`. If you see logs named `followupd_*.crash`, disable the faulty service with `launchctl remove com.apple.followupd` For any other errors, pray that the crash logs are not empty, open them to see what the issue is, and google a way to fix it. Afterwards, clear the logs from the folder with `find ~/Library/Logs/DiagnosticReports/ \-mindepth 1 \-delete` :upside_down_face:

Revision: 2551 by @irhett in #[IM @irhett] 2 years agoSlack Archive

If your iterm is running slow, `cd ~/Library/Logs/DiagnosticReports ; open .` then open one of the latest crash file (right click on the file in Finder) and read the crash report to find what the issue is. Usually deleting the erroneous folder in question ( `~/Library/Suggestions` ) solves the problem. Then just `rm ~/Library/Logs/DiagnosticReports`. If the file list is too long, learn you a google ¯\_(ツ)_/¯

Revision: 2367 by @jkrause in #cadets-old 2 years agoSlack Archive

If your iTerm is slow, run the following: `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` 

You should insert that command into your `~/.zshrc` with the following modifications, so your iTerm will never run slow again. 
`find ~/Library/Logs/DiagnosticReports -mindepth 1 -delete >/dev/null 2>&1 &`
If your iTerm is slow, run the following: `find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` 
If your iTerm is slow, run the following:`find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete` 
&1
If your iTerm is slow, run the following:'find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete' 

Revision: 1699 by @sjones in <!error getting other user for D3T7YKTH6> 2 years agoSlack Archive

&2

Revision: 1698 by @sjones in <!error getting other user for D3T7YKTH6> 2 years agoSlack Archive

If your iTerm is slow, run the following:'find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete' 

Revision: 1697 by @sjones in <!error getting other user for D3T7YKTH6> 2 years agoSlack Archive

If your iTerm is slow, run the following: 'find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete' 

Revision: 1696 by @sjones in <!error getting other user for D3T7YKTH6> 2 years agoSlack Archive

find ~/Library/Logs/DiagnosticReports/ -mindepth 1 -delete 

Revision: 197 by @kyork in #cadets-old 2 years agoSlack Archive

If your iTerm is slow, run the following: `find ~/Library/Logs/DiagnosticReports/ -delete`

Revision: 177 by @kyork in #unix 2 years agoSlack Archive

If your iTerm is slow, run the following:
`find ~/Library/Logs/DiagnosticReports/ -delete`
And follow the directions here: http://apple.stackexchange.com/questions/211062/repeated-crashes-of-suggestd

Revision: 105 by @crenfrow in #teamwork 2 years agoSlack Archive

If your iTerm is slow, run the following `rm -rf ~/Library/Logs/DiagnosticReports/*.crash` Afterwards you may want to add the same command to your .zshrc to prevent them from building up again.

Revision: 95 by @crenfrow in #[IM @crenfrow] 2 years agoSlack Archive

If your iTerm is slow: `rm -rf ~/Library/Logs/DiagnosticReports/`