Solaris 10 Troubleshooting Guide Pdf

But we can redirect it to a file. So it does not update any changes. Cron facility can be used to schedule regularly occurring commands or scripts. The best way to edit a crontab is using the command crontab -e.

Important cron files

Solaris 10 Operating System (Solaris 10 1/06 - Solaris 10 1/13)

Here is an another video by Gabriel Smith that I would like to share on how to do basic performance troubleshooting in Solaris. This post will help to get started with some basic performance monitoring and troubleshooting. Unfortunately, knowledge management pdf 2008 Brenden does not have a video explicitly on the usage of sar and prstat for performance monitoring and troubleshooting.

How to edit a crontab

Oracle Solaris 10 1/13 Documentation2. mpstat Key fields

The uptime command gives us the load averages along with the system uptime information. Run the following command only if the previous command completes successfully, i. Take the following character literally. It is good to know some of the redirection and special symbols being used when adding an entry to the crontab. Check for the period in which the scripts should have run in the cron log.

The video discusses the key fields in the about of vmstat command and how to interpret them. This will print the date every minute to the console. Many a times cron jobs fail because the password has expired for the user owning the job.

Oracle Solaris 10 8/11 Documentation

In my opinion one of the hardest thing to do by any system admin is to pin point the exact cause of performance bottleneck. One of the reasons of this is a wrong permission to cron and crontab.

The post contains some of the excellent videos by Brenden Gregg. Many of us struggle to do this. When ed starts up it prints the number of characters in the crontab file and does not have a prompt. To avoid this, simple com out of the ed editor by typing q.

But he has well explained it, how to use them along with the other tools discussed above. Below are few of the troubleshooting tips and best practices which can be helpful in many cases. Seems silly, but I have seen many people doing this mistake of not giving executable permissions to the script they want to run from cron. The video explains about the key fields in the output of mpstat and how to interpret them to analyze a performance issue. Any mistake in using them may again lead to a cron job failure.

Normally stdin is from the keyboard and stdout and stderr goes to the terminal. If you delete all the cron jobs using crontab -e, the command crontab -l will still show all the cron jobs.