Of course (I said "other than giving the absolute path"), but with bsync 2.1.4 it was different: if btsync was started with --nodaemon --log sync.log, sync.log was created in ${storage_path}, not the current directory. I used that in a simple upstart script, and there was no need to parse $conf to extract storage_path. Something has changed in 2.2