Not sure who should handle this (kazoo or user), but if chroot directories chain doesn't exist - ensure path fails with NoNodeException
Hmm... Seems like it's not an easy task for a client to create chroot directories if we created KazooClient passing chroot in hosts.
We could do a "exists" call on client startup and see if the chroot node is present. If it isn't, we could at least throw a more meaningful error message.
That could help a lot
- Issue #53: Throw a warning upon starting if the chroot path doesn't…
so that it's more obvious when the chroot should be created before
performing more operations.
I've added a warning to the start() method that warns if the chroot doesn't exist. This seems like the sanest part since throwing an exception could likely be undesireable and change the API substantially.
Yes, that's better than nothing, thanks!