Dear FSVS developers, I've toyed around with creating something similar to the functionality of FSVS, but with a very strong focus on a) centralized gathering of system configuration (via Subversion) b) centralized reporting/review c) determining the cause of a file's change via audit trails or at least by who was logged in (via the submitting host at the time the change is logged) d) tracking the output of program output (cleaning out date/time strings) for changes
If I were to investigate expanding FSVS to determine the cause of changes (especially in /etc), do you believe the framework would support this? I've sort of gathered that you don't use Subversion in the core, which probably forces you to reinvent the wheel in a few places. Is this assumption true? Thanks, Charlie Todd chtodd-AT-christian.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
