Fixing Mac OS X Permissions from Terminal

I support a lot of Macs and it’s much easier to work on them remotely via SSH to do things like permission fixes, ACL repairs and other sneaky things. Here’s how to repair permissions from SSH/Terminal:

diskutil repairPermissions /

Of course you may need to sudo or use the su command to do this.

You can also do a repair disk this way too but that may dismount the users active drive so use with caution:

diskutil repairdisk /

 

Mac OS Log and Crash Report Locations for OS X 10.7, 10.8, 10.9

Within Mac OS X, crash reports are saved in various locations depending on which version of Mac OS X you have installed.

Since I work with 10.7.x and greater here are the ones I’m most interested in:

Mac OS X 10.7/10.8/10.9

In Mac OS X 10.7, 10.8, 10.9 crash logs are saved in the ‘Library’ folder which is hidden by default. To locate the Library folder, choose ‘Go to Folder’ from  Finder’s ‘Go’ menu and type:

~/Library/Logs/DiagnosticReports/

TIP: To make the Library folder permanently visible in Mac OS X 10.7/10.8/10.9, type the following command in Terminal:

chflags nohidden ~/Library

A look in there will look like this. Notice that Indesign has been a bad program lately:

Adobe Illustrator_2014-06-23-151424_NY05-0020.crash	
Adobe InDesign CS6_2014-07-03-193002_NY05-0020.crash	
Adobe InDesign CS6_2014-07-04-162801_NY05-0020.crash
Adobe InDesign CS6_2014-06-23-170943_NY05-0020.crash	
Adobe InDesign CS6_2014-07-03-193036_NY05-0020.crash	
Adobe InDesign CS6_2014-07-04-162943_NY05-0020.crash
Adobe InDesign CS6_2014-07-03-154725_NY05-0020.crash	
Adobe InDesign CS6_2014-07-03-193510_NY05-0020.crash	
Adobe InDesign CS6_2014-07-04-163221_NY05-0020.crash
Adobe InDesign CS6_2014-07-03-155019_NY05-0020.crash	
Adobe InDesign CS6_2014-07-03-193829_NY05-0020.crash	
Adobe InDesign CS6_2014-07-04-163312_NY05-0020.crash
Adobe InDesign CS6_2014-07-03-155534_NY05-0020.crash
Google Chrome Helper_2014-06-07-094200_NY05-0020.crash

If you’re logged on from SSH and you’re not the user in question you can use sudo to see the users logs, just use the path below with the user name:

~/Users/username/Library/Logs/DiagnosticReports

Happy troubleshooting!

 

 

 

 

Mac OS X Screen Shot Commands

I started like with a Mac Classic running System 5, then slowly moved to newer Macs running System 6, 7 , 8 and 9. Then I started working mostly on Windows. I take it for granted that Windows has a single key for screenshots and now an app to do partials.
Naturally I now support lots of Macs and I finally need to learn the Mac versions. So here they are:

Command-Shift-3

This captures a screenshot of your entire screen/screens.

Command-Shift-4

This turns the cursor into a crosshair, which you can drag to select a portion of your screen to capture. Release the mouse button or trackpad to take the shot.

Command-Shift-4, then space bar, then click on a window

Hitting the space bar turns the crosshair into a little camera icon, which you can move over any open window. Click on your desired window to take a screenshot of it. A screenshot captured by this method features a white border around the window with a bit of a drop shadow.

All screenshots are dropped on the desktop as an image file.

And if you happen to be using Log Me In to make the screenshots on the remote computer the screen shots won’t appear on the remote desktop…they show up on your local desktop….

Sending Syslog logs from Ubuntu to a remote syslog server

I don’t know why I didn’t have notes on this already. I’ve done it dozens of times. So here’s the write up.

I use Ubuntu and it uses the syslog facility/daemon called rsyslogd. Its configuration file is located here:

/etc/rsyslog.d/50-default.conf

This file tells the deamon where to log each type of message. For example the follow entry means that all cron message are sent to /var/log/cron.log:

cron.* /var/log/cron.log
Continue reading

My place for thoughts, random brain droppings and my projects.

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: