search for: everlasting

Hullo :) I'm using CVS-04/23/04-23 from the stable 1.0 branch on kernel 2.6 - since I have no Digium h/w, I've just managed to get the zaprtc module to compile and run, so I thought the best way to test it would be via MoH. The MP3Player application works great .. exten => 6901,1,Answer exten => 6901,2,MP3Player(http://127.0.0.1:85/ES/28) This will play callers BBC Radio 4 from

Can anyone explain why BackgrounDRb is switching form DRb to SMTP protocol? That seems like a lot of overhead to add to the messaging back and forth? Orion

I''m getting the following error (when doing script/backgroundrb start) on my local machine, which is running os x 10.4.11. However, it works just fine on my linux server. RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in `dump_object'': undefined method `write_nonblock'' for #<UNIXSocket: 0x135b5f4> (NoMethodError) I just grabbed the

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

is there an easy way to disable logging to backgroundrb_debug.log? Regards - reynard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080102/195dee18/attachment.html

...s is just a by product of using "packet" library. I know, thing is rough around the edge and needs more polish. But still, i hope it will be more stable than previous versions of backgroundrb. Please report all the bugs here. Thanks -- 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

...ed in... I'll probably find out tomorrow when I have an online class.) Anyone have any ideas how to get control over this? thanks! -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

Hey guys, I was playing with the cron trigger, and I noticed that wday is not honored. Looking at the code confirms this. Has anyone else seen this? Thanks Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20071217/44d3a8a6/attachment.html

...ts : ** Ezra Zygmuntowicz,skaar for taking BackgrounDRb so far. ** Kevin for helping out with OSX issues. ** Andy for patches and initial testing. ** Paul for patching up README. ** Other initial users. ** Matz, Francis for general inspiration. -- 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

I''m running the latest from svn (rev 285). I''ve been having a problem launching a process repeatedly. What happens is that I get a debug message "some read error" and then the worker refuses to run again. I''ve stripped my worker down to just doing a puts and it still happens. Like the other threads I want to launch my workers as needed, however I get the

Hello, Does reload_on_schedule force the worker to be reloaded even if it is already running? Or does it just load the worker if its not running when the schedule fires? I want to load the worker at the scheduled time if its not running, but I don''t want to reload the worker if its already running. Make sense? Thanks, Scott

...avoid the network in one of the following ways > > 1. Store installed packages on your local drive > 2. Copy the installed packages to a tempdir on your local drive each time > the script is executed > 3. Keep an R session running in perpetuity and source the scripts within > that everlasting session > 4. Rewrite your scripts to use base R only. > > I suspect this solution list is exhaustive. > > On Mon, 20 Jul 2020 at 1:50 am, Mario Annau <mario.annau at gmail.com> wrote: > >> Dear all, >> >> in our current setting we have our packages stored o...

...been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory and do a rake backgroundrb:setup and you should be good to go. -- 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

...w it runs timers and can trigger callbacks. So progress bar example, will have to reworked using callback mechanism, rather than threads. PS: trunk doesn''t yet reflect the changes i said. I will be checking in code soon. stay tuned. -- 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

...gt; >For Centos 7, I use Mate from the epel repo. I assume it'll eventually >appear there for C8 as well. > >-- >---- Fred Smith -- fredex at fcshome.stoneham.ma.us >---------------------------- > Do you not know? Have you not heard? >The LORD is the everlasting God, the Creator of the ends of the earth. >He will not grow tired or weary, and his understanding no one can >fathom. >----------------------------- Isaiah 40:28 (niv) >----------------------------- >_______________________________________________ >CentOS mailing list >CentOS...

Hi, I am trying to get the scheduling to work with my RoR application. How do I determine what version of backgroundrb I have configured? When I try to invoke??? rake backgroundrb:setup? , it fails. Thanks for the help. Linda

Hi All, When I add the line ''reload_on_schedule true'' to my worker, my tests will no longer run with the following exception: Starting ferret DRb server.../Users/revelation/projects/revelation-project/config/../lib/workers/alert_worker.rb:3: undefined method `reload_on_schedule'' for AlertWorker:Class (NoMethodError) class AlertWorker < BackgrounDRb::MetaWorker

Since moving to r296, I get warnings (" warning: already initialized constant...") for many of my class constants. This did not happen before, and I do not get the same warnings when loading my application normally. They are only warnings, so everything still runs, but I thought I would provide the FYI. -- Dave Dupre -------------- next part -------------- An HTML attachment was

Hi, I would like to use backgroundrb inside a story, been trying to set this up for a while, but I think the only solution is to use fixture files and unit testing. The problem is that every time I call a new worker, the test database gets wiped out, and only has available the records in fixture files. Instead, it would be great if the test database maintains its state throughout the

Most of the useful audacity stuff is in their wiki: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux seems like a good place to start.