Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, has anyone experimented with logwatch on Solaris? If so what are your opinions. We currently have a script that basically dumps our /var/adm/message file for all our systems. Sometimes we get blank emails because nothing occurred sometimes we are bombarded with bootup messages. I am looking for a way to monitor the logs for suspicious activity such as ssh failed logins and basically system messages such as the disk suite failing or other hardware components failing. Logwatch on Linux is great but does anyone here use it for Solaris?
I have no experiences on logwatch. My opinion is as follows.
- For logging ssh activity to /var/adm/messages. Add one line to /etc/syslog.conf and restart syslog daemon, then
test the ssh loggin setting by ssh -l <username> <server_ip>
auth.info /var/adm/messages ==> you also can use one file to log ssh activity only.
Solaris9: /etc/init.d/syslog stop ==> Start
Solaris10: svcadm restart system/system-log
- About disk info, I always checked the following commands. You can man these commands. If disk has some errors, /var/adm/messages
should log disk errors with timestamp. And if you are using disk array, some monitor s/w shold be available for your array.
# format
# iostat -En
- /usr/platform/`uname -i`/sbin/prtdiag -v can show you system healthy.
Your idea is good but I would like a system that will email me daily logs of all my systems and highlight suspicious items such as failed attempts etc. Logwatch on Linux is great I just was wondering if anyone used it for Solaris or if it even is possible. I don't want to manually SSH into each system to look at the /var/adm/messages file for all systems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.