Files
community.general/library
Rune Kaagaard 27ab2e55d3 Service mod.: Proper(?) handling of return code 69
This adds "69" to the return codes from the status command that should be
considered as not running. At least "django-celery" uses this return code,
maybe others::

    /venv/bin/python /code/project/manage.py celeryctl status
    echo $? # 69 when not running.

A bit of googling let me to http://tldp.org/LDP/abs/html/exitcodes.html and
on a Ubuntu Server 12.10 I get::

    ~# cat /usr/include/sysexits.h | grep 69
    #define EX_UNAVAILABLE	69	/* service unavailable */

I'm not sure if the content of sysexits.h is the same on other OS'es.
2013-01-17 10:13:05 +01:00
..
2012-11-21 18:49:30 +01:00
2013-01-13 11:24:21 -08:00
2012-11-21 18:49:30 +01:00
2013-01-10 16:21:18 +01:00
2013-01-13 11:24:21 -08:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2013-01-13 11:24:21 -08:00
2012-10-29 13:10:23 +01:00
2013-01-10 19:24:23 +01:00
2013-01-13 11:24:21 -08:00
2012-10-23 15:14:01 +02:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2012-11-21 18:49:30 +01:00
2013-01-13 11:24:21 -08:00
2013-01-13 11:24:21 -08:00
2013-01-04 16:36:02 +10:00
2012-11-27 11:18:46 -05:00