| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
Otherwise we will crash if no args are passed. Now we print the usage message
|
|
|
|
|
|
|
|
|
|
* 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
|
|
|
|
|
|
--run-once will exit once all current changes have been processed
--rerun will process all users again even those that were processed before
--overwrite-security will overwrite security for user databases even
if it has been set before.
|
|
Pathname makes dealing with files easier than String.
Tapicero will look for design documents in design directory in the tapicero path for now.
|
|
|
|
|
