I just went and grabbed the nightly-build RPM to get some changes in GIT into
my system, and discovered that I once again have database errors when
violations is being reread.
After digging into it, I found that at some point "class_set_defaults" has
been removed, so the default values are not being propagated from "default"
violation into the empty slots on other violations.
Is there are reason for this? I see that a "-default" option has been added
to the definition of $cached_violations_config, but I don't see any logic in
there that actually moves values into place prior to populating the database.
If this is simply an incomplete change in directions, I'll put the old stuff
back in for now and proceed.
Thanks.
Don
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
PacketFence-devel mailing list
PacketFence-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
