NSMnow 1.3.1 … Where did sancp go?

A small regression was introduced with the feature freeze of 1.3 which was preventing sancp data from showing up in the sguil client.

To cut a long story short the sancp_agent was looking for data in one location whilst sancp was reporting it in another. This has been fixed.

Another small fix was with some distributions cleaning up the /var/run directory on reboot. This directory as well as /var/log are now dynamically created as appropriate prior to starting a particular service.

This update does not require a full NSMnow re-install, but rather you can take advantage of just downloading the NSMadministration tarball and overwriting the existing NSM Adminstration scripts and library files in /usr/local/sbin and /usr/local/lib respectively.

Thanks go to Doug for identifying these pesky bugs.

Leave a Reply