So I was typing some things in Terminal and after a while, I decided to use (sudo powermetrics --samplers smc |grep -i “CPU die temperature") to check CPU temperature but I was greeted with (pipe dquote>). Now would anyone know how to exit this? I already tried looking it up but it isn't helping. Any help is appreciated!
MacBook Pro 13″, macOS 10.15
In the Terminal, just type control+c to break out of the command expecting you to complete its syntax. Don't type control+z as that just throws the session in the background.
For Intel platforms only (notice the spacing around the pipe symbol).
sudo powermetrics -n 1 --samplers smc | grep "(CPU|GPU) die"
This was from a just booted Core i7 iMac:
There is no safety net on the command line except for what the user creates themselves by making sure any affected files are backed up. Nothing you discussed in this thread should have made any changes to your environment or macOS. Also, we have no way of knowing all the commands you ran or any files which you may have modified.
Be extremely careful using any commands found on the Internet without fully understanding what those commands and each option with those commands will do. You can get more information on each individual command by reviewing the manual "man" pages for each command which will also tell you what each option does. For example, for the commands mentioned in this thread you could check what each one by running these commands:
man sudo
man powermetrics
man grep
Be extremely careful when using "sudo" because it gives the command following it full root (aka admin) access which can very easily cause you to break macOS or even accidentally delete all your data without any way of recovering it except from a backup since data deleted using the command line does not go to the Trash. Without "sudo " pre-pending the command your local user data is still at risk from a mistake, but it does minimize accidents occurring outside of your home user folder. Keep in mind that even users with years of command line experience have been known to make a simple mistake that has had terrible repercussions....sometimes just because of a simple typographical error.
Something new learned today - thx 👍
Look more closely at my syntax above. No parenthesis, and white-space between the pipe symbol and grep. Emulate what works.
I was running Monterey 12.5.1 on that Core i7 iMac for that previous screenshot, and here is one from just a few minutes ago on the same iMac:
Alright got it. I don't think I ran any commands besides the CPU temp one and I didn't notice anything out of the orginary afterwards.
Okay so this should be it. Thanks for both of your help VikingOSX and HW Tech! Greatly appreciated!
Mac Terminal
