Undocumented HS behavior with relative paths
Tor accepts relative paths for HiddenServiceDir...
>>> GETCONF HiddenServiceOptions 250-HiddenServiceDir=hidden_service_example 250 HiddenServicePort=80 127.0.0.1:5000
This seems to result in the HiddenServiceDir being relative of the tor process' cwd, rather than the DataDir which I kinda expected. This is all well and good, but should be noted in the manpage.
It's a tiny bit unfortunate that 'GETCONF HidddenServiceOptions' then provides back relative paths, since controllers need to read the HiddenServiceDir to determine the hostname (at least until legacy/trac#1949 (moved)), but not a terribly big whoop. :)