Comments on: 7 Basic Solaris Troubleshooting Tips http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/ How to build an infrastructure based on UNIX Wed, 19 Nov 2008 23:24:34 +0000 http://wordpress.org/?v=2.6.2 By: Geraldine Sullivan http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-392 Geraldine Sullivan Thu, 13 Nov 2008 02:32:59 +0000 http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-392 8dnzgaqr4zpuxjz2 8dnzgaqr4zpuxjz2

]]> By: pro review activ solution http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-381 pro review activ solution Sat, 20 Sep 2008 13:05:02 +0000 http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-381 pro activ solution proactiv <a href="http://www.al.com/forums/profile.ssf?nickname=colin259" rel="nofollow">pro solution treatment activ</a> pro activ solution proactiv pro solution treatment activ

]]> By: Nickus http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-65 Nickus Wed, 11 Jul 2007 18:29:00 +0000 http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-65 Indeed, I shouldn't have forgotten that. I even wrote a blog post about some weeks ago - <a href="http://aspiringsysadmin.com/blog/2007/06/13/how-to-use-smf-to-quickly-detect-problems/" rel="nofollow">How to use SMF to quickly detect problems</a> Indeed, I shouldn’t have forgotten that. I even wrote a blog post about some weeks ago - How to use SMF to quickly detect problems

]]> By: James Dickens http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-61 James Dickens Wed, 11 Jul 2007 13:13:40 +0000 http://aspiringsysadmin.com/blog/2007/06/29/7-basic-solaris-troubleshooting-tips/#comment-61 If you are working with Solaris 10 or later systems, you should always run svcs -x to see which services are not running, It will even provide you log locations to see if the bad event that caused any problems left info about the failure. svc:/application/print/server:default (LP print server) State: disabled since Wed Jul 11 08:11:44 2007 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: lpsched(1M) Impact: 1 dependent service is not running. (Use -v for list.) If you are working with Solaris 10 or later systems, you should always run svcs -x to see which services are not running, It will even provide you log locations to see if the bad event that caused any problems left info about the failure.

svc:/application/print/server:default (LP print server)
State: disabled since Wed Jul 11 08:11:44 2007
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 1 dependent service is not running. (Use -v for list.)

]]>