search for: triggerd

...et i found this "explanation": "LDAP_CONSTRAINT_VIOLATION Indicates that the attribute value specified in a modify, add, or modify DN operation violates constraints placed on the attribute. The constraint can be one of size or content (string only, no binary)." Hm, is this triggerd by dns-updates? I see this only with two clients How can I "debug" this ? I am using samba 4.3.4 with bind-dlz clients are win7 Thank you for your thoughts! Markus

I''m sure this has been asked before but a quick search on the web didn''t give me any hints.. I''d like to do this: @person = Person.find_by_name throw_page_not_found unless @person Anybody know how to do this, do I have to manually tinker with the response object? -- Posted via http://www.ruby-forum.com/.

Is there any way that you could trigger events based upon actual pickup of calls and hangups of lines in ALL cases(parked calls, queued calls, calls triggerd by .call queue files)? It seems like Asterisk needs something a little lower level to allow for this, is it even possible? MATT--- -----Original Message----- From: asterisk@analitica.md [mailto:asterisk@analitica.md] Sent: Thursday, October 09, 2003 8:57 AM To: asterisk-users@lists.digium.com Su...

...fsnotify triggering to kernfs_notify() which requires a sleepable context. There are already existing users of kernfs_notify() which invoke it from an atomic context and in general it's silly to require a sleepable context for triggering a notification. The following is an invalid context bug triggerd by md invoking sysfs_notify() from IO completion path. BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586 in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffff...

...fsnotify triggering to kernfs_notify() which requires a sleepable context. There are already existing users of kernfs_notify() which invoke it from an atomic context and in general it's silly to require a sleepable context for triggering a notification. The following is an invalid context bug triggerd by md invoking sysfs_notify() from IO completion path. BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586 in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffff...

...IOLATION > > Indicates that the attribute value specified in a modify, add, or > > modify DN > > operation violates constraints placed on the attribute. The > > constraint can be > > one of size or content (string only, no binary)." > > > > Hm, is this triggerd by dns-updates? > > I see this only with two clients > > How can I "debug" this ? > > > > I am using samba 4.3.4 with bind-dlz > > clients are win7 > > > > Thank you for your thoughts! > > > > Markus > > > -- > Adam Tauno W...

...> "LDAP_CONSTRAINT_VIOLATION > Indicates that the attribute value specified in a modify, add, or > modify DN > operation violates constraints placed on the attribute. The > constraint can be > one of size or content (string only, no binary)." > > Hm, is this triggerd by dns-updates? > I see this only with two clients > How can I "debug" this ? > > I am using samba 4.3.4 with bind-dlz > clients are win7 > > Thank you for your thoughts! > > Markus > -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D9...

Dear All, My Requirement is 1. I am taking backup from client to server and i configured floating IP Address at the client 2. From primary or secondary server rsync command will be triggerd via floating IP Address to the client PC I am using the following rules in firewall scripts /sbin/iptables -F INPUT /sbin/iptables -F OUTPUT /sbin/iptables -F FORWARD /sbin/iptables -F RH-Firewall-1-INPUT # Default Rule /sbin/iptables -P OUTPUT ACCE...

...notify() which requires a > sleepable context. There are already existing users of > kernfs_notify() which invoke it from an atomic context and in general > it's silly to require a sleepable context for triggering a > notification. > > The following is an invalid context bug triggerd by md invoking > sysfs_notify() from IO completion path. > > BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586 > in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1 > 2 locks held by swapper/1/0: > #0: (&(&vblk->vq_lock)-&gt...

https://bugzilla.mindrot.org/show_bug.cgi?id=2467 Bug ID: 2467 Summary: point-to-point Tunnel doen't work since 6.8 Product: Portable OpenSSH Version: 7.1p1 Hardware: amd64 OS: Linux Status: NEW Severity: major Priority: P5 Component: sshd Assignee: unassigned-bugs at

...at the attribute value specified in a modify, add, or > > > modify DN > > > operation violates constraints placed on the attribute. The > > > constraint can be > > > one of size or content (string only, no binary)." > > > > > > Hm, is this triggerd by dns-updates? > > > I see this only with two clients > > > How can I "debug" this ? > > > > > > I am using samba 4.3.4 with bind-dlz > > > clients are win7 > > > > > > Thank you for your thoughts! > > > > >...

Add support for a xenstore dm command to flush qemu''s buffer cache. qemu will just keep mapping pages and not release them, which causes problems for the memory pager (since the page is mapped, it won''t get paged out). When the pager has trouble finding a page to page out, it asks qemu to flush its buffer, which releases all the page mappings. This makes it possible to find

On 06/29/2014 02:47 PM, Michael S. Tsirkin wrote: > On Sun, Jun 29, 2014 at 09:32:22PM +0200, Christoph Hellwig wrote: >> On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote: >>> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote: >>>> Hi All, >>>> >>>> We've had a report[1] of the virt_blk driver causing a lot of

On 06/29/2014 02:47 PM, Michael S. Tsirkin wrote: > On Sun, Jun 29, 2014 at 09:32:22PM +0200, Christoph Hellwig wrote: >> On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote: >>> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote: >>>> Hi All, >>>> >>>> We've had a report[1] of the virt_blk driver causing a lot of

...0.00 76.00 *199.00* 0.65 0.78 10.66 0.02 0.07 0.16 0.04 0.07 *1.85* Stuff i've checked/tried: - The data in the cached LV has then not exceeded even half of the space, so this should not happen. It even happens when only 20% of cachedata is used. - It seems to be triggerd most of the time when %cpy/sync column of `lvs -a` is about 30%. But this is not always the case! - changing the cachepolicy from cleaner to smq, wait (check flush ready with lvs -a) and then back to smq seems to help /sometimes/! But not always... lvchange --cachepolicy cleaner /dev/mapper/XXX...

...> 10.66 0.02 0.07 0.16 0.04 0.07 *1.85* > > > Stuff i've checked/tried: > > - The data in the cached LV has then not exceeded even half of the space, > so this should not happen. It even happens when only 20% of cachedata is > used. > - It seems to be triggerd most of the time when %cpy/sync column of `lvs > -a` is about 30%. But this is not always the case! > - changing the cachepolicy from cleaner to smq, wait (check flush ready > with lvs -a) and then back to smq seems to help *sometimes*! But not > always... > > lvchange --cachepoli...

I've got configuration which in simple includes combination of afrs and unify - servers exports n[1-3]-brick[12] and n[1-3]-ns and client got cluster configuration: volume afr-ns type cluster/afr subvolumes n1-ns n2-ns n3-ns option data-self-heal on option metadata-self-heal on option entry-self-heal on end-volume volume afr1 type cluster/afr subvolumes n1-brick2

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Version: 2.2.12 OS: Debian wheezy x86_64 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Panic: file mail-index-map.c: line 547 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Fatal: master: service(imap): child 2760 killed with signal 6 (core dumped) GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation,