similar to: disregard RE: new syntax for autostart and repeat

Hello: I''m a little confused as to the >0.20 brb syntax as it relates to autostart and repeat. In short, I''d like to know the easiest way to automatically start a worker and have it repeat every xx minutes. This was easy in the previous version because you would simply do : ''repeat.every 20.minutes'' or similar in the worker. I''m sure

Hi, Does backgroundrb 0.2.1 support autostart? I''ve tried to set up autostart by adding something like the following in backgroundrb.yml: autostart: 1: class: bar_worker args: '''' However, that does not seem to work. I also tried the scheduling mechanism like this in backgroundrb_schedules.yml: bar: :class: :bar_worker :job_key: :bar1

Hi gang, Thanks to other help I''ve gotten on this list, I''ve got backgroundrb up and running using postgres alongside my rails app. I''ve designed the system to have several eternally-running workers that periodically poll the database to see if there''s any work for them to do, and set things up in the config file to make them restart quickly if any of them

Hi there, Backgroundrb is working pretty well for me but I have a job that launches two of the same job, apparently a minute(?) apart from each other. Should this be happening if I have repeat interval enabled with a job_key? It seems like it should wait until the job is finished before launching a new instance. --Backgroundrb_schedules.yml-- city_updater: :class: :city_updater_worker

Hello all, I'm running a newly installed CentOS 5.4 KVM host and am running into problems setting guests up to autostart. Has anyone seen and/or overcome this issue? [root at virt04 ~]# virsh autostart guest02 error: Failed to mark domain guest02 as autostarted error: internal error cannot set autostart for transient domain Just for kicks I tried symlinking /etc/libvirt/guest02.xml and

Hello there, CentOS6.7 64-bit up-to-date running on my laptop.. This night I had to restart (did it properly). Since then, my ~/.config/autostart/ contains some new broken .desktop files and /var/log/messages complains: gnome-session[7280]: WARNING: Could not parse desktop file /home/wwp/.config/autostart/gnome-keyring-daemon.desktop: Key file does not have key 'Name'

Following xml file was used to create storage pool using 'virsh pool-create <xml>' <pool type='dir'> <name>my-diskpool</name> <uuid>2fbc894e-7619-6cda-a33c-b27fae5fbe8b</uuid> <capacity>136024670208</capacity> <allocation>11416657920</allocation> <available>124608012288</available> <source>

hi all I've a few guest which work/run perfectly fine, I believe, except for autostart. Configuration of system, gluster and libvirt is pretty regular and not complex. Errors I see: ... failed to initialize gluster connection (src=0x7f9424266350 priv=0x7f94242922b0): Transport endpoint is internal error: Failed to autostart VM 'rhel-work2': failed to initialize gluster connection

Hello guys, Recently I have switched to use LVM cache feature on logical volume /dev/hdd/windata1 to improve it performace using 32GB partition from SSD disk. However, when my computer will start, my virtual machine won't autostart Mar 21 10:48:57 brutus-coreos libvirtd[956]: Cannot access storage file '/dev/hdd/windata1' (as uid:107, gid:107): No such file or directory Mar 21

I have a host running a few guests all configured to autostart. I'm also using libvirt-guests to suspend the guests when the host restarts or shuts down When the host comes back up I see a bunch of log messages - Resuming guest vm01 already active Resuming guest vm02 already active I guess this is because libvirt autostarts the guests when it starts and before libvirt-guests has a chance to

Hi guys, I have Centos 5.2 with all updates. I am using xen virtualization - with visrsh. I want to have autostart of domains configured, but so far this does not work [root at power ~]# virsh autostart reqdemo libvir: error : this function is not supported by the hypervisor: virDomainSetAutostart error: Failed to mark domain reqdemo as autostarted I know that , when i am using xm style

On Tue, Mar 21, 2017 at 1:37 AM, ıuoʎ <yonjah@gmail.com> wrote: > On Mon, Mar 20, 2017 at 9:58 PM, Timo Juhani Lindfors > <timo.lindfors@iki.fi> wrote: > > ıuoʎ <yonjah@gmail.com> writes: > >> I have a host running a few guests all configured to autostart. > >> I'm also using libvirt-guests to suspend the guests when the host > >>

On Mon, Mar 20, 2017 at 9:58 PM, Timo Juhani Lindfors <timo.lindfors@iki.fi> wrote: > ıuoʎ <yonjah@gmail.com> writes: >> I have a host running a few guests all configured to autostart. >> I'm also using libvirt-guests to suspend the guests when the host >> restarts or shuts down > > I have a similar setup. I solved it by writing a small daemon that syncs

Hello all, I''ve got the problem about the following simple application using autostart and repeat_every. A thread(?) is forked for processing task at first, but at sencond time two threads seem to be forked. My simple application code is... - In worker class class FooWorker < BackgrounDRb:Rails repeat_every 2.minutes first_run Time.now def do_work puts Time.now.to_s +

Devs, compiz listmates: Why can't I turn off compiz autostart on openSuSE 10.3 i386? Compiz just decided to start automatically with KDE login ever since I upgraded to the first 0.7.4.x release from the openSuSE build service. I have tried to disable it by creating the file "disable-compiz" in ~/.config/compiz but compiz still starts at login. Even if I switch to kwin before

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

I have a feeling my no autostart problem is related to the following tests in compiz-manager. Is there a way I can "step" through the script on openSuSE 10.3 while it is running to find out where the script dies? Or do I basically have to insert error returns throughout the script to capture that info? ---- # if we run under Xgl, we can skip some tests here if ! check_xgl; then # if

I want to know if libvirt supporting qemu domain Autostart? my libvirt version is 0.9.8. xuanmao_001 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120716/5fd5dedb/attachment.htm>

Hi I started setting up tinc 1.1 and it works great. only thing is I am not able to configure it to autostart. How is this done in 1.1? I used to use nets.boot file to get it running. Regards <yazeedfataar at hotmail.com> -------------- next part -------------- An HTML attachment was scrubbed... URL:

Maybe trivial question, but I cannot find an answer: How to autostart Asterisk (daemon) on Slackware 10? I know that I should put something in /etc/rc.d, but what?