Added doc for -C option for config directory
CONFIG_DIR to CONFD_PATH
allow specifying multiple zmq addresses to bind/connect
move zmq address config parsing into _main_parser
fix zmq transport tests
Allow string escapes in delimiter

As far as I can tell, there is no way for me to represent a newline as
a delimiter in a configuration file with ConfigParser. I want to do this:

      [/ephemeral_storage/logs/kind_of_special.log]
      tags: special
      type: special
      delimiter: \n\n

As the log has a blank line between its multiline entries.

My change allows that, by making delimiter not string-escaped until
after the config file is parsed. I'm naive about python, so there is a
strong possibility I've gone about it horribly wrong. This would also
easily allow splitting on nulls, tabs, unicode characters and other
things that ConfigParser may not find kosher.

By doing this sort of multiline parsing with beaver, it allows one to
run logstash without the multiline filter, which due to its lack of
thread-safety, forces you to run logstash with only one worker thread.
Redis 2.4.11 is no longer available on Pypi

Fixes issue #167
Merge pull request #168 from andrewgross/patch-1

Redis 2.4.11 is no longer available on Pypi
Fixed example in Readme.rst for sqs_aws_secret_key
Allow path to be None

Allow path to be set empty (None) in the configuration filer. This way
all files and globs can be configured in files in confd_path.
Merge pull request #159 from ohlol/master

Allow connecting or binding to multiple zmq addresses
Merge pull request #171 from romabysen/master

Allow path to be empty in configuration file.
Merge pull request #169 from jonathanq/master

Fixed example in Readme.rst for sqs_aws_secret_key
Merge pull request #153 from iyingchi/master

Added some missing confd docs
Merge pull request #165 from meekmichael/meekmichael/allow_string_escapes_in_delimiter

Allow string escapes in delimiter
Use os._exit over sys.exit in signal handlers to quit cleanly

As per
http://thushw.blogspot.co.uk/2010/12/python-dont-use-sysexit-inside-signal.html
the use of `sys.exit` inside the signal handlers means that a
`SystemExit` exception is raised
(http://docs.python.org/2/library/sys.html#sys.exit) which can be caught
by try/except blocks that might have been executing at time of signal
handling, resulting in beaver failing to quit
Merge pull request #179 from doismellburning/signal_handler_exit

Use os._exit over sys.exit in signal handlers to quit cleanly
Release version 30
Removed duplicate self._current_host from @source field. Fixes #180.
Merge pull request #181 from adesso-mobile/master

Deduplication of source host information