tapicero.git/bin, branch master

bugfix: pid file was not created correctly on startup. closes #6338

2014-11-10T23:54:22+00:00

check for ARGV.first before testing it

2014-07-01T08:22:20+00:00

Otherwise we will crash if no args are passed. Now we print the usage message

pid issue remains to be solved - revert to sth working

2014-07-01T08:20:24+00:00

We've seen two instances of tapicero running on the production servers. The reason is that we are using two different places for the pid file - one for root and one for a normal user.

In this scenario tapicero started by root will not notice the tapicero run as a normal user and vice versa. One idea was to solve this by always using /var/run/pid. However this also requires write privileges to that place which essentially only root has.

So let's keep the two different places and just make sure we ALWAYS run tapicero as the same user.

check for ARGV.first before testing it

2014-06-27T09:21:20+00:00

Otherwise we will crash if no args are passed. Now we print the usage message

initial take on replication

2014-06-23T13:33:11+00:00

hand config files on the command line to the daemon

2014-02-04T10:46:57+00:00

first interesting tests

2014-02-04T10:46:57+00:00

try to get require rubygems to work on travis

2014-02-04T10:46:57+00:00

make logging more precise

2014-01-03T14:28:49+00:00

* do not log the SystemExit after the fork
* log error classes alongside messages
* unify logging in retry_request_once
* debug now logs every step
* info has one message per user created
* warn only logs errors during the actions
* error only logs crashes

better debug loggin, sleep before retrying

2014-01-03T13:50:04+00:00