![[BACK]](/icons/back.gif){kind=icon}
Up to [local] / ports / devel / ruby-daemon_controller
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.3, Wed Sep 6 09:30:23 2023 UTC (8 months, 3 weeks ago) by jeremy
Branch: MAIN
CVS Tags: HEAD
Changes since 1.2: +0 -0 lines
FILE REMOVED
Remove ruby-daemon_controller Last release was over 9 years ago, and upstream appears dead. Pure Ruby port, and nothing depends on it. If you need this, use gem install. OK sthen@ rsadowski@
Revision 1.2 / (download) - annotate - [select for diffs], Thu Jun 26 14:45:53 2014 UTC (9 years, 11 months ago) by jeremy
Branch: MAIN
CVS Tags: OPENBSD_7_3_BASE,
OPENBSD_7_3,
OPENBSD_7_2_BASE,
OPENBSD_7_2,
OPENBSD_7_1_BASE,
OPENBSD_7_1,
OPENBSD_7_0_BASE,
OPENBSD_7_0,
OPENBSD_6_9_BASE,
OPENBSD_6_9,
OPENBSD_6_8_BASE,
OPENBSD_6_8,
OPENBSD_6_7_BASE,
OPENBSD_6_7,
OPENBSD_6_6_BASE,
OPENBSD_6_6,
OPENBSD_6_5_BASE,
OPENBSD_6_5,
OPENBSD_6_4_BASE,
OPENBSD_6_4,
OPENBSD_6_3_BASE,
OPENBSD_6_3,
OPENBSD_6_2_BASE,
OPENBSD_6_2,
OPENBSD_6_1_BASE,
OPENBSD_6_1,
OPENBSD_6_0_BASE,
OPENBSD_6_0,
OPENBSD_5_9_BASE,
OPENBSD_5_9,
OPENBSD_5_8_BASE,
OPENBSD_5_8,
OPENBSD_5_7_BASE,
OPENBSD_5_7,
OPENBSD_5_6_BASE,
OPENBSD_5_6
Changes since 1.1: +2 -5 lines
Diff to previous 1.1 (unified)
Update to daemon_controller 1.2.0. Thanks sthen@ for the reminder
Revision 1.1.1.1 / (download) - annotate - [select for diffs] (vendor branch), Thu Nov 17 15:33:29 2011 UTC (12 years, 6 months ago) by jeremy
Branch: jeremy
CVS Tags: jeremy_2011-Nov-17,
OPENBSD_5_5_BASE,
OPENBSD_5_5,
OPENBSD_5_4_BASE,
OPENBSD_5_4,
OPENBSD_5_3_BASE,
OPENBSD_5_3,
OPENBSD_5_2_BASE,
OPENBSD_5_2,
OPENBSD_5_1_BASE,
OPENBSD_5_1
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (unified)
Import ruby-daemon_controller 0.2.6
daemon_controller is a library for starting and stopping specific
daemons programmatically in a robust, race-condition-free manner.
It's not a daemon monitoring system like God or Monit. It's also not a
library for writing daemons.
It provides the following functionality:
Starting daemons. If the daemon fails to start then an exception
will be raised. daemon_controller can even detect failures that
occur after the daemon has already daemonized.
Starting daemons is done in a race-condition-free manner. If another
process using daemon_controller is trying to start the same daemon,
then daemon_controller will guarantee serialization.
daemon_controller also raises an exception if it detects that the
daemon is already started.
Connecting to a daemon, starting it if it's not already started.
This too is done in a race-condition-free manner. If the daemon
fails to start then an exception will be raised.
Stopping daemons.
Checking whether a daemon is running.
OK ajacoutot@
Revision 1.1 / (download) - annotate - [select for diffs], Thu Nov 17 15:33:29 2011 UTC (12 years, 6 months ago) by jeremy
Branch: MAIN
Initial revision