What was the error? (Any exception or error is most welcome, for faster response). What you basically need is that gem to be in path and packet_worker_runner to be in PATH. There might be some issues with relative paths, but i think, it should just work.
Try running backgroundrb without daemonizing it, and post the exceptions. On Thu, Aug 28, 2008 at 3:02 PM, Iain <[EMAIL PROTECTED]> wrote: > hemant kumar wrote: >> >> Folks, have reported some problems with running frozen gems, but it >> should be rather trivial to fix. Let me know, if you figured it out(in >> that case, I welcome a patch) or I will look into asap. >> >> >> On Tue, 2008-08-26 at 18:32 +0100, Iain wrote: >> >>> >>> Hi, >>> >>> I have written an application that uses backgroundrb and everything was >>> working fine. Now I am ready for deployment I have frozen the gems into the >>> vendors directory of my rails app. I then removed the gems from my local >>> machine as a test to see if backgroundrb was using the frozen gems. Now I am >>> getting errors. It says it can't find the source. Does this mean that >>> backgroundrb does not work with frozen gems? Has anyone come across this >>> problem before? >>> >>> Thanks >>> >>> Iain >>> _______________________________________________ >>> Backgroundrb-devel mailing list >>> [email protected] >>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>> >> >> > > Hermant, > > The only Gem I am having trouble with is Packet. I think this is because it > adds packet_worker_runner to the /usr/bin directory. I thought I could > reference the gem copy in the PATH variable but doesn't seem to work. Any > ideas? > > Thanks > > Iain > -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
