My /home/myusername/ directory is provided through a network, and looks exactly the same on my Linux machine and my Mac Mini. I'd like to add to PATH a directory of Mac-specific software in my home, e.g. /home/myusername/SW/bin_mac/ and have this happen only when I'm doing command line stuff on the Mac, and not have PATH contain this when on Linux. If I edit .bashrc (or tcsh's equivalent) it'll affect PATH in both cases. What are some tricks to do this?
Adding Mac-specific directory to PATH when home is shared
command linepath
Related Solutions
Option #1) you may consider using inbuilt utility powermetrics to get the cpu and gpu temperature and lot more other details.
To get CPU temperature:
sudo powermetrics --samplers smc |grep -i "CPU die temperature"
To get GPU temperature:
sudo powermetrics --samplers smc |grep -i "GPU die temperature"
To get lot more details:
sudo powermetrics
This has been tested on macbook pro with macOS mojave.
Option #2) Install Intel® Power Gadget officially provided by Intel from here
Intel® Power Gadget and then launch Intel Power Gadget from the launchpad.
Result Screen:
If you fix the typo in your PATH assignment and replace usr/local/bin with /usr/local/bin Homebrew should stop complaining.
The other stuff (/opt/local/...) is definitively added somewhere later during shell initialization (meaning after source ~/.bashrc or after . ~/bin/dotfiles/bash/env). You will have to look through the different files (or grep for /opt/local or PATH.*PATH) to see where it happens (and why).
Related Question
- Removing Built-in Command-Line Utilities from PATH in zsh – macOS Guide
- MacOS – Help on setting path right
- MacOS – How -exactly- do I remove a specific directory, from the PATH, in OSX, Mavericks
- How to Export to $PATH Permanently Without .bashrc File
- How to Connect a router to console, using a mac
- PATH – Adding a New Directory to PATH Variable
- macOS – Fix Bash Commands Not Working in Terminal
- Fix Terminal PATH Issue – How to Fix Terminal Hang After Editing PATH in .bash_profile
Best Answer
Test the output of
uname; it will beDarwinon OS X andLinuxon Linux.Alternately, you could just add an appropriate directory on each machine, which will be useful if you find yourself needing a separate Linux
bindirectory as well in the future.and either
mvorln -syourbin_mactobin_Darwin; then you can create abin_Linuxdirectory in the future if you need it, and it'll just work.(You could also test
$HOSTTYPE, which is set bybash, but it contains more information than you're likely to need.)