AUTOMATICALLY IDENTIFYING CONFIGURATION FILES

[1]  Erez Zadok,et al.  A Versatile and User-Oriented Versioning File System , 2004, FAST.

[2]  Peter M. Chen,et al.  Whither generic recovery from application faults? A fault study using open-source software , 2000, Proceeding International Conference on Dependable Systems and Networks. DSN 2000.

[3]  Norman C. Hutchinson,et al.  Deciding when to forget in the Elephant file system , 1999, SOSP.

[4]  Martin Szummer,et al.  Snitch: interactive decision trees for troubleshooting misconfigurations , 2007 .

[5]  Richard P. Martin,et al.  Understanding and Validating Database System Administration , 2006, USENIX Annual Technical Conference, General Track.

[6]  George Candea,et al.  Microreboot - A Technique for Cheap Recovery , 2004, OSDI.

[7]  Mark Sullivan,et al.  Software defects and their impact on system availability-a study of field failures in operating systems , 1991, [1991] Digest of Papers. Fault-Tolerant Computing: The Twenty-First International Symposium.

[8]  Yuanyuan Zhou,et al.  Rx: treating bugs as allergies---a safe method to survive software failures , 2005, SOSP '05.

[9]  Geoffrey M. Voelker,et al.  NetPrints: Diagnosing Home Network Misconfigurations Using Shared Knowledge , 2009, NSDI.

[10]  Wei Zheng,et al.  Automatic configuration of internet services , 2007, EuroSys '07.

[11]  Steven D. Gribble,et al.  Configuration Debugging as Search: Finding the Needle in the Haystack , 2004, OSDI.

[12]  Ricardo Bianchini,et al.  Staged deployment in mirage, an integrated software upgrade testing and distribution system , 2007, SOSP.

[13]  Patrick Goldsack,et al.  SmartFrog Meets LCFG: Autonomous Reconfiguration with Central Policy Control , 2003, LISA.

[14]  Helen J. Wang,et al.  Strider: a black-box, state-based approach to change and configuration management and support , 2003, Sci. Comput. Program..

[15]  Helen J. Wang,et al.  Automatic Misconfiguration Troubleshooting with PeerPressure , 2004, OSDI.

[16]  Angelos D. Keromytis,et al.  ASSURE: automatic software self-healing using rescue points , 2009, ASPLOS.

[17]  Mona Attariyan,et al.  Using Causality to Diagnose Configuration Bugs , 2008, USENIX Annual Technical Conference.

[18]  Paul Anderson,et al.  LCFG: The Next Generation , 2002 .

[19]  Ronald L. Rivest,et al.  Introduction to Algorithms , 1990 .

[20]  George Forman,et al.  Finding similar files in large document repositories , 2005, KDD '05.

[21]  Jim Gray,et al.  Why Do Computers Stop and What Can Be Done About It? , 1986, Symposium on Reliability in Distributed Software and Database Systems.

[22]  Jason Flinn,et al.  Automatically Generating Predicates and Solutions for Configuration Troubleshooting , 2009, USENIX Annual Technical Conference.

[23]  Mahadev Satyanarayanan,et al.  Disconnected Operation in the Coda File System , 1999, Mobidata.

[24]  Archana Ganapathi,et al.  Why Do Internet Services Fail, and What Can Be Done About It? , 2002, USENIX Symposium on Internet Technologies and Systems.

[25]  Peter A. Dinda,et al.  Wayback: A User-level Versioning File System for Linux (Awarded Best Paper!) , 2004, USENIX Annual Technical Conference, FREENIX Track.

[26]  L. Alvisi,et al.  A Survey of Rollback-Recovery Protocols , 2002 .

[27]  Jason Nieh,et al.  Transparent Checkpoint-Restart of Multiple Processes on Commodity Operating Systems , 2007, USENIX Annual Technical Conference.

[28]  Ashvin Goel,et al.  Reconstructing system state for intrusion analysis , 2008, OPSR.

[29]  Samuel T. King,et al.  Recovery domains: an organizing principle for recoverable operating systems , 2009, ASPLOS.

[30]  Fred B. Schneider,et al.  Hypervisor-based fault tolerance , 1996, TOCS.

[31]  Yuanyuan Zhou,et al.  Understanding Customer Problem Troubleshooting from Storage System Logs , 2009, FAST.

[32]  George Varghese,et al.  Automated Worm Fingerprinting , 2004, OSDI.

[33]  David A. Patterson,et al.  Undo for Operators: Building an Undoable E-mail Store , 2003, USENIX Annual Technical Conference, General Track.

[34]  Wei-Ying Ma,et al.  Automated known problem diagnosis with event traces , 2006, EuroSys.

[35]  Mary Baker,et al.  The Recovery Box: Using Fast Recovery to Provide High Availability in the UNIX Environment , 1992, USENIX Summer.

[36]  Samuel T. King,et al.  Debugging Operating Systems with Time-Traveling Virtual Machines (Awarded General Track Best Paper Award!) , 2005, USENIX Annual Technical Conference, General Track.

[37]  Kishor S. Trivedi,et al.  A comprehensive model for software rejuvenation , 2005, IEEE Transactions on Dependable and Secure Computing.

[38]  Craig A. N. Soules,et al.  Metadata Efficiency in Versioning File Systems , 2003, FAST.

[39]  Jim Gray,et al.  A census of Tandem system availability between 1985 and 1990 , 1990 .

[40]  Evan Marcus,et al.  Blueprints for high availability , 2000 .

[41]  B. Karp,et al.  Autograph: Toward Automated, Distributed Worm Signature Detection , 2004, USENIX Security Symposium.

[42]  Richard P. Martin,et al.  Understanding and Dealing with Operator Mistakes in Internet Services , 2004, OSDI.

[43]  Jason Nieh,et al.  Proceedings of the 5th Symposium on Operating Systems Design and Implementation , 2022 .

[44]  Randal C. Burns,et al.  Ext3cow: a time-shifting file system for regulatory compliance , 2005, TOS.

[45]  Mona Attariyan,et al.  AutoBash: improving configuration management with operating system causality analysis , 2007, SOSP.

[46]  Yennun Huang,et al.  Software rejuvenation: analysis, module and applications , 1995, Twenty-Fifth International Symposium on Fault-Tolerant Computing. Digest of Papers.

[47]  David A. Patterson,et al.  Rewind, repair, replay: three R's to dependability , 2002, EW 10.

[48]  Kiran-Kumar Muniswamy-Reddy,et al.  Causality-based versioning , 2009, TOS.

[49]  Peter M. Chen,et al.  Exploring failure transparency and the limits of generic recovery , 2000, OSDI.