On 08/25/2011 11:43 AM, Miroslav Suchý wrote: > On 08/25/2011 02:30 PM, Johannes Renner wrote:
> >> - While most of the struts actions are RhnAction or RhnLookupDispatchAction, >> there is still some that are not derived from these classes. Therefore it's >> not enough to put a shortcut method to the logger in the(se) >> superclass(es). In a way this high lights some of the technical hurdles that would need to be tackled in any 'auditing' capability for Spacewalk or Satellite. Do you do it within the schema (and loose the who from where did what - unless all app code passes it down to DB). Do you do it say in Apache where you have IP addresses, GET/POST and other details - but you got no idea what is in the SSM for session, so that delete POST for SSM of lots of systems still doesn't know what was deleted. Touching *lots* of code to me is likely the main way to achieve this and any implementation will be up for heated discussion on best approach. Still reading the thread, I'm very interested to see where this goes. Cliff > > Exactly, if you go from bottom (base classes) you can be never sure if > log all childs and getting the big picture will be very hard. And you > could not be really sure till you test it. > > _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
