Setting up SNMP (Simple Network Management Protocol) on a CentOS machine is a very quick and easy process and I often forget so here’s a quickie on how.
Install the SNMP daemon by running the following command:
yum install net-snmp
Once SNMP is installed you want to install the configuration utility. I always forget this. It makes it easy to configure SNMP for both the community string, SNMP version and basic security.
yum install net-snmp-utils
Once the configuration tool is installed, run it:
snmpconf -g basic_setup
As you run through the configuration utility it will present you with many options. Depending on how you have your remote monitoring setup (Cacti/Nagios) you will need to choose the options that work for you.
Once done, you will need to copy the configuration file to the correct directory. In most cases it will need to be moved from “/root/snmpd.conf” to “/etc/snmp/snmpd.conf” – You will need to overwrite the existing conf file in the /etc/snmp/ directory.
mv /root/snmpd.conf /etc/snmp/
Once the configuration file has been moved over you can restart SNMP.
service snmpd restart
The last thing you need to do is have SNMP start at boot time. If you do not run the following command you will need to manually start SNMP after a reboot.
chkconfig snmpd on
At this point you should be set. If for some reason you are running the firewall will need to open port 161 for UDP & TCP traffic to allow SNMP to be accessed remotely.
Let me start by saying that HP has some of the worst drivers for their small office printers. Shame on you!
After many rounds with “re-installing”, specifically HP drivers, I found that it was better to just manually wipe them from the computer and start over.
Open a command prompt with administrative privileges and enter:
net stop spooler
Navigate to (Paste one of these paths into the run command:
NOTE: %systemroot% is usually C:\Windows, but it might be “winnt” or something else; this is set when the OS is installed. Most systems are like this C:\Windows\system32\spool\drivers\w32x86 but also note that if you’re using a 64-bit version of windows the drivers will be in the folder called x64
Inside the w32x86/x64 folder there will be other folders and files. Delete the contents of these folders but do not delete them.
Restart the computer and re-install the printer.
Make sure you turn off or unplug the printer if it’s directly attached. If you don’t Windows will try and be smart and reinstall it for you.
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 /
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:
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 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:
I’m always amazed at Jeopardy contestants so here’s a tip:
You can win with $1
Risking it all may seem like a good idea but if everyone did that and you were left with $1 you’d be a winner.
NY State lottery says it best- a dollar and a dream….
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:
This captures a screenshot of your entire screen/screens.
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….
Since I rehosted with WordPress.com some of the articles didn’t move over properly. Things are missing like slashes and what not. I ‘ll be fixing them over time but if you spot one let me know.