Skip to search form
Skip to main content
Skip to account menu
Semantic Scholar
Semantic Scholar's Logo
Search 218,237,303 papers from all fields of science
Search
Sign In
Create Free Account
Crash-only software
Known as:
Crash-only
Crash-only software refers to computer programs that handle failures by simply restarting, without attempting any sophisticated recovery. Correctly…
Expand
Wikipedia
(opens in a new tab)
Create Alert
Alert
Related topics
Related topics
9 relations
Autosave
Computer program
Crash (computing)
Erlang
Expand
Papers overview
Semantic Scholar uses AI to extract papers important to this topic.
2015
2015
Infrastructure Safety Assessment in a Connected Vehicle Environment
Brian L. Smith
,
Robert Kluger
,
Hyungjun Park
2015
Corpus ID: 1801038
The goal of the Infrastructure Safety Assessment in a Connected Vehicle (CV) Environment project was to develop a method to…
Expand
2013
2013
Early-deciding consensus is expensive
D. Dolev
,
C. Lenzen
ACM SIGACT-SIGOPS Symposium on Principles of…
2013
Corpus ID: 2723145
In consensus, the <i>n</i> nodes of a distributed system seek to take a consistent decision on some output, despite up to <i>t</i…
Expand
2011
2011
Improving reliability of Minix3 through crash-only software
Hui Cao
,
Chao Tong
,
J. Niu
,
Yuhang Gao
6th International Conference on Computer Sciences…
2011
Corpus ID: 12035755
In the traditional reliable system, a simple reboot of failed service is not the optimal solution for higher reliability. This…
Expand
2008
2008
Failure Semantics in a SOA Environment
C. Hobbs
,
H. Becha
,
Daniel Amyot
International Conference on eTechnologies
2008
Corpus ID: 19960046
In a Service-Oriented Architecture (SOA), services publish descriptions to permit their composition into larger services. There…
Expand
2007
2007
The Fail-Heterogeneous Architectural Model
M. Serafini
,
N. Suri
IEEE International Symposium on Reliable…
2007
Corpus ID: 2770127
Fault tolerant distributed protocols typically utilize a homogeneous fault model, either fail-crash or fail-Byzantine, where all…
Expand
2007
2007
A Case for Heterogeneous Architectures
M. Serafini
,
N. Suri
2007
Corpus ID: 10261971
Fault tolerant distributed protocols are typically designed using a homogeneous fault model, either crash-only or Byzantine…
Expand
2007
2007
Crash-only Components in Self-healing Systems
Toni Ruottu
2007
Corpus ID: 16221908
Crash-only components don’t provide a method for shutting them down. Therefore crash recovery functionality gets tested every…
Expand
2007
2007
Carrying the Crash-Only Software Concept to the Legacy Application Servers
Javier Alonso
,
J. Torres
,
L. Silva
CoreGRID Workshop - Making Grids Work
2007
Corpus ID: 747776
In the last few years, high-availability on internet services has become a main goal for the academia and industry. We all know…
Expand
2006
2006
Research on Microreboot and Design of Crash-only Software
Wang Hui
2006
Corpus ID: 63439344
Microreboot is a new technology for fast and cheap recovery applied for large-scale distributed application system. This paper…
Expand
Highly Cited
2003
Highly Cited
2003
Crash-Only Software
George Candea
,
A. Fox
USENIX Workshop on Hot Topics in Operating…
2003
Corpus ID: 262751434
Crash-only programs crash safely and recover quickly. There is only one way to stop such software--by crashing it--and only one…
Expand
By clicking accept or continuing to use the site, you agree to the terms outlined in our
Privacy Policy
(opens in a new tab)
,
Terms of Service
(opens in a new tab)
, and
Dataset License
(opens in a new tab)
ACCEPT & CONTINUE