Closed vulpinelogic closed 15 years ago
Scrap that... quoting the path causes the Dir[] call to return an empty array in master_proxy. Back to square one...
Duh... Fixed it at the root of the problem in packet_worker_runner. Don't know why I was trying to work around it in backgroundrb. Now lets see if I can get the packet maintainers to add the patch...
Seems like for some time now, backgroundrb version 1.1 has been plaguing certain users with a "no such file" error for log_worker when starting up the backgroundrb server. It hit me today, and the cause quickly became apparent. Somewhere around version 0.1.7, packet's code changed in some way that causes WORKER_ROOT or WORKER_LOAD_ENV paths with spaces in them to cause a no such file error. It has to do with the way packet constructs the command line for packet_worker_runner.
While it would probably make more sense for the maintainers of packet to fix this issue on their end, the fix in backgroundrb is really simple. Just add preceding and trailing " characters to WORKER_ROOT and WORKER_LOAD_ENV.
I'd submit a patch myself, but I'm really new to ruby and not sure if my fix would be considered the "right way" to go about working around the packet issue. I plan on mentioning this to the packet maintainers too.