Pros and Cons of using logrot.pl over Solaris logadm utility for LMS v3.2
I've been going back and forth with development on a way of best leveraging a log rotation capability in our newly deployed LMS 3.2 rollout on Solaris 10.
As of now, we use the services facility built into Solaris to start/stop the syslog service and logrotate (via logadm) our LMS log file (syslog_info) on a weekly basis. I added an argument in logadm to HUP the syslogd service which I think resets the file pointer and/or forces syslogd service to re-read the syslog.conf file. The problem with this setup is that in order for me to logrotate, I additionally have to stop and start a whole chain of processes so that the LMS application can carry on its duties of collecting and analyzing this data. So what I would have to do without drilling down a lenghty process dependencies is to stop/restart LMS which I really dislike doing for a small part of the entire application suite.
Cisco TAC recommends that insead of using logadm, that we should use logrot.pl which I have used in the past on a limited basis. TAC informs me that this will essentially logrotate and stop/start the LMS as well but what I haven't been able to get out of them is how this script deals with the syslog service. I looked over the code but didn't see any reference to the actual syslog service.
The main advantage of logrot is that it rotates the file in place without modifying the inode number. It also hass some Daemon Manager knowledge built in. With syslog_info, logadm is perfectly fine provided you use the "-c" argument to logadm. This will do an in-place rotation, and no daemons will need to be restarted.
Listen: https://smarturl.it/CCRS8E37Follow us: twitter.com/ciscochampionSometimes, situations require temporary fixes. Sometimes, the network becomes an afterthought in overall office design and planning. In either situation, it may require netw...
In this special edition of the Insider Series, we hear from Cisco partners who have taken steps to be more eco-friendly and sustainable. We hear what inspires ASHRAE, Southwire, Igor, and NTT to create a workplace that is centered around people and how th...
We know that the Type-1 LSA describes the link type connected to the router, the neighbor router and the subnet number.In this topology, assume we dont have a Type-2 LSA, so each router will create its own Type-1 LSA, the Type-1 LSA will describe the neig...
Here are some commonly asked questions and answers to help with your adoption of Cisco DNA Center Wireless. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Q. I have a Cisco Appl...
Why IETF changed and inverted OSPF Type-7 LSA VS Type-5 LSA election In RFC 3101 compared to OLD RFC 1587?Many people learns that the Type-7 LSA and Type-5 election (ON Versus OE routes) depends on RFC 3101 for NSSA published in 2003 and RFC 1587 for NSSA...