Hey guys,

I just re-ran some chef-recipes I had and noticed how CouchDB 1.0.1
didn't start (/etc/init.d/couchdb) return 1.
So I updated the recipe to use 1.0.2 and found the same problem.

After adding 'set -x' to the script, I discovered that the 'su' call
failed. Has anyone else seen this?
I replaced both (for start and stop) with sudo -u $COUCHDB_USER
$command which makes it work, but I reckon sudo is not too portable
across the different flavours of Linux.

I think the most clean and consistent approach is start-stop-daemon,
but I wanted to ask here first before I write a patch.

Till

Reply via email to