0.0
Low commit activity in last 3 years
A long-lived project that still receives updates
The original bluepill process monitor worked well. In 2013 several changes were introduced that were detrimental to the stability of bluepill, as well as the system running it. This fork reverts back to the stable/non-destructive code.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 1.0.10
~> 0.9
!= 0.9.0
~> 1.0
~> 0.7

Runtime

~> 1.1.4
>= 0.5.0
 Project Readme

Why this fork?

Bluepill worked well for us on http://ridewithgps.com up through version 0.0.60, after which they introduced the process journal. The Process journal is a flawed idea - persist to disk a journal of all PIDs underneath a watched process in bluepill. Due to a variety of bugs, PIDs end up in the journal (sometimes growing uncontrollably, filling log files with gigs of data) well after the original process has exited. Given that PIDs are not unique and are in fact regularly reused, and that Bluepill kills all processes with PIDs in the journal file when it is restarted, terrible bugs ensue. If not running privileged, bluepill dies. If running privileged, other unintended processes die.

This fork will likely not be maintained, aside from ensuring it works with updated ruby versions.

Bluepill

Bluepill is a simple process monitoring tool written in Ruby.

Check out the original Bluepill repo for information about the tool: http://github.com/bluepill-rb/bluepill