search for: balrog

...virsh attach-device ShadowFax kingston.xml El dispositivo fue asociado exitosamente virsh detach-device ShadowFax kingston.xml El dispositivo fue desmontado exitosamente which means the device is succesfully attached but is never seen in the vm The records in /var/log/messages: Sep 30 21:34:57 Balrog libvirtd: 21:34:57.288: warning : qemudParsePCIDeviceStrs:1411 : Unexpected exit status '1', qemu probably failed Sep 30 21:35:07 Balrog libvirtd: 21:35:07.803: warning : qemudParsePCIDeviceStrs:1411 : Unexpected exit status '1', qemu probably failed Sep 30 21:35:07 Balrog libvirtd:...

I am a beginner so please excuse me, if i am doing something totally wrong. I have created a class using "wsdl2ruby.rb" and here is what it looks like: class ServiceSoap < ::SOAP::RPC::Driver DefaultEndpointUrl = "http://balrog/services/SearchWorker/service.asmx" MappingRegistry = ::SOAP::Mapping::Registry.new Methods = [ ... -- Posted via http://www.ruby-forum.com/.

...uch > the compiler's responsibility. I agree the compilers should know about threads, but enough to work around the issues and not start creating threads the user didn't ask for. I'm not against enhancing the compiler to that point, I just think that you're digging too deep and Balrog might show up unexpectedly. Thread issues can be daunting by themselves, automatically creating threaded code is a recipe to disaster, IMHO. > Again, my vote is to define vector atomics as respecting atomicity across > elements and make it the compiler's and user's job to know when...

On Tuesday 27 April 2010 12:16:26 Renato Golin wrote: > I'm not against enhancing the compiler to that point, I just think > that you're digging too deep and Balrog might show up unexpectedly. > Thread issues can be daunting by themselves, automatically creating > threaded code is a recipe to disaster, IMHO. Eventually all compilers are going to have to create threads. The architecture roadmap demands it. > > Again, my vote is to define vector a...

...r.rb:240:in `synchronize'' (druby:/localhost:9010) /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:8:in `synchrolock'' (druby:/localhost:9010) /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:267:in `<<'' (druby:/localhost:9010) /var/www/rails/balrog/releases/20070628045633/vendor/plugins/acts_as_ferret/lib/local_index.rb:263:in `reindex_model'' ..... Has anybody else had this before? Any ideas what could have caused it? It''s only happened once. I''m using ferret 0.11.4 and aaf trunk. Cheers, -Jonathan. -- Post...

...none of the excluded files or files deleted in the source are getting deleted from the snapshot. rsnapshot calls rsync like this: /usr/bin/rsync -a --delete --numeric-ids --relative --delete-excluded \ --exclude-from=/home/omen/.backup/rsnapshot \ /home/ \ /var/cache/rsnapshot/snapshots/daily.0/balrog/ When I run the same command but add '--dry-run -v -v' I get a single line about deleting files: deleting in home/. Then it moves on to showing the uptodate files. If I remove the trailing slash from '/home/' in the command, then I get the line: deleting in home deleting [snip]...

...must be rebuilt after every deploy. I guess the simplest solution would be to put it under log/ which is already shared by capistrano, any other ideas? Also, script/ferret_stop doesn''t work when run on a fresh deploy without a index/ dir. It gives an error like: /home/jviney/Workspace/balrog/vendor/plugins/acts_as_ferret/lib/act_methods.rb:1 88:in `open'':Errno::ENOENT: No such file or directory - /home/jviney/Workspace/b alrog/index/production/person Even though it is set up to use DRb, it wrongly expects the index to be present. Aaf shouldn''t do anything with a loca...

On Tuesday 27 April 2010 11:01:16 Renato Golin wrote: > On 27 April 2010 16:46, David Greene <dag at cray.com> wrote: > > It shouldn't be very hard for the compiler to detect the second case. > > It's a pretty straightforward pattern.  For everything else it would > > have to assume case #1. > > The only problem is that threads are rarely within language

On Tuesday 27 April 2010 13:16:14 David Greene wrote: > On Tuesday 27 April 2010 12:16:26 Renato Golin wrote: > > I'm not against enhancing the compiler to that point, I just think > > that you're digging too deep and Balrog might show up unexpectedly. > > Thread issues can be daunting by themselves, automatically creating > > threaded code is a recipe to disaster, IMHO. > > Eventually all compilers are going to have to create threads. The > architecture roadmap demands it. And it's not the d...

On 27 April 2010 16:46, David Greene <dag at cray.com> wrote: > It shouldn't be very hard for the compiler to detect the second case. > It's a pretty straightforward pattern.  For everything else it would > have to assume case #1. The only problem is that threads are rarely within language specs, so the compiler would have to choose one particular flavour of threads or