phlax

hi @ehough - the only thing i wasnt 100% sure about is the optimal settings for retry etc - these seemed reasonable defaults - but not sure

i guess the issue with the grace period is significant here

> The problem is that exportfs's exit code seems like it's always 0 wierd, i tested this when i made the PR and have been using it since. Not sure...

after a little playing with this, i have come to the conclusion that this healthcheck should probs not be added to the base image, for a few reasons - checking...

~~also - i might be wrong - but i think this does work after all (it seems to in my deployment)~~ try this: ``` docker run --rm alpine sh -c...

although not sure 8/ ``` $ docker run -ti --rm alpine sh / # apk add nfs-utils && exportfs fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz (1/15) Installing krb5-conf (1.0-r1) (2/15) Installing libcom_err...

this seems to work, but not sure about performance or how reliable ``` / # nfsstat -s Error: No Server Stats (/proc/net/rpc/nfsd: No such file or directory). / # echo...

@ehough shall i close this? i think its probs best to leave to individual setups etc

im thinking this issue is not related to the grace period, and may well not be a problem. Not sure how to test the client-tracking

@friedelwolff github is defo good for discussing specific issues - but for more immediate discussion we are generally on https://gitter.im/translate/dev