How does SCC differ from other similar configuration collectors? What are some of the strengths and weaknesses of SCC?
Siem Korteweg: SCC collects configuration data without formatting it immediately to HTML. Instead it prefixes each line of configuration data with fix/var and a hierarchical classification. This makes it easy to process the snapshots. The processing consists of comparing consecutive snapshots to generate the logbook, formatting the snapshot to HTML and comparing the snapshots of two systems to determine the differences. The philosophy of SCC is to collect data, not to judge its value or correctness. Stupid configuration errors in Apache/Samba are not detected in scc, this should be done at the server where all snapshots are collected. Some might question the value of all the data in the snapshots. It is true that a considerable part of the snapshots will never change during the lifetime of a system. Nevertheless this data is collected, just in case someone needs it sometimes. One commercial configuration collector works by allowing remote root-access to all clients from their server. T
Related Questions
- How does SCC differ from other similar configuration collectors? What are some of the strengths and weaknesses of SCC?
- How does Spa for the Spirit differ from the ordinary day spa experience? In what ways is it similar?
- What are some of the specific strengths and weaknesses of the different types of teeth whiteners?
