search for: notifc

I have searched quite a few places and have not seen this discussed. Basically I was wondering how would you go about having an option for a user to be notified every 15 minutes until their new voicemail message is checked. Since the notification e-mails we send get sent to cell phones or actual pagers (via e-mail), there are times when a person is out of range and misses a page or just simply

...[753]: Data for UPS [UPSdevice] is stale - check driver Apr 19 12:09:26 laney upsd[753]: UPS [UPSdevice] data is no longer stale Seems that during the 'onbattwarn' event, NUT lost communcaiton with the UPS for about 6 secs? this is really quick to trigger any 'COMM_BAD' evebt so no notifcation regarding this is sent, just the logs. However as stated above on the logs, just 1 min later (12:10:21) power is totally lost even from UPS, no trace of LowBattery events, comm errors or so. A part from a email message that upssched sent me (although no logs of the event appears), this email...

...+#include <linux/pci-epf.h> > +#include <linux/pci-epc.h> > +#include <linux/vringh.h> > +#include <linux/dmaengine.h> Alpha order if possible > + /* Virtual address of pci configuration space */ s/pci/PCI/ > + /* Callback function and parameter for queue notifcation > + * Note: PCI EP function cannot detect qnotify accurately, therefore this > + * callback function should check all of virtqueue's changes. > + */ Multi-line comment style. Bjorn

...f --git a/include/linux/vdpa.h b/include/linux/vdpa.h > index 239db794357c..cebc79173aaa 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -87,6 +87,11 @@ struct vdpa_device { > * @vdev: vdpa device > * @idx: virtqueue index > * Returns the notifcation area > + * @get_vq_irq: Get the irq number of a virtqueue > + * @vdev: vdpa device > + * @idx: virtqueue index > + * Returns u32: irq number of a virtqueue, > + * -EINVAL if no irq assigned. I think we can not get -EINVAL since the function will return a u32. Th...

...2..07fcf5e6abc8 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -169,6 +169,12 @@ struct vdpa_map_file { > * @vdev: vdpa device > * @idx: virtqueue index > * Returns the notifcation area > + * @get_vq_notification_pgprot: Get the pgprot of the vq's notification area (optional) > + * @vdev: vdpa device > + * @idx: virtqueue index > + * @prot: original page protection...

...ial data? I've already considered a number of workarounds including copying the messages right from the file system but the only way to get things like email notification is to use the function. Is there a copy function that I could use in a loop that would also notify anyone with an email notifcation set up? Any help or guidance would be appreciated. Thanks in advance, -Don

Please forgive me if this is a stupid question. If it has been answered already, please point me to the answer, as my searching has been fruitless. How can I programatically handle 404s and 500s when using Mongrel? I''ve read about using a proxy server config (.htaccess for example) to render an ErrorDocument rather than whatever comes from Rails, but I need something different. I would

...e] is stale - check > driver > Apr 19 12:09:26 laney upsd[753]: UPS [UPSdevice] data is no longer stale > > Seems that during the 'onbattwarn' event, NUT lost communcaiton with the > UPS for about 6 secs? this is really quick to trigger any 'COMM_BAD' evebt > so no notifcation regarding this is sent, just the logs. > > However as stated above on the logs, just 1 min later (12:10:21) power is > totally lost even from UPS, no trace of LowBattery events, comm errors or > so. A part from a email message that upssched sent me (although no logs of > the eve...

Since we've switched to spoolss printing (samba 2.2.4) it seems that the server is always trying to connect to the client. [2002/06/11 10:52:41, 3] lib/util_sock.c:open_socket_out(843) Connecting to 10.0.40.80 at port 445 [2002/06/11 10:52:41, 2] lib/util_sock.c:open_socket_out(871) error connecting to 10.0.40.80:445 (Connection refused) [2002/06/11 10:52:41, 3]

From ba9abf6ee7e5fe0515e2d51b14743c8d5416285c Mon Sep 17 00:00:00 2001 From: Liu, Jinsong <jinsong.liu@intel.com> Date: Fri, 24 Feb 2012 02:18:02 +0800 Subject: [PATCH 2/2] Xen pad logic This patch implement Xen pad logic, and when getting pad device notification, it hypercalls to Xen hypervisor for core parking. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> ---

PCIe endpoint framework provides APIs to implement PCIe endpoint function. This framework allows defining various PCIe endpoint function behaviors in software. This patch extend the framework for virtio pci device. The virtio is defined to communicate guest on virtual machine and host side. Advantage of the virtio is the efficiency of data transfer and the conciseness of implementation device

Hi all: This series introduce basic functionality of doorbell mapping support for vhost-vDPA. Userspace program may use mmap() to map a the doorbell of a specific virtqueue into its address space. This is help to reudce the syscall or vmexit overhead. A new vdpa_config_ops was introduced to report the location of the doorbell, vhost_vdpa may then choose to map the doorbell when: - The doorbell

Hi all: This series introduce basic functionality of doorbell mapping support for vhost-vDPA. Userspace program may use mmap() to map a the doorbell of a specific virtqueue into its address space. This is help to reudce the syscall or vmexit overhead. A new vdpa_config_ops was introduced to report the location of the doorbell, vhost_vdpa may then choose to map the doorbell when: - The doorbell

...lar VMCI Sockets, please refer to the VMCI Socket Programming Guide available at https://www.vmware.com/support/developer/vmci-sdk/. --- George Zhang (12): VMCI: context implementation. VMCI: datagram implementation. VMCI: doorbell implementation. VMCI doorbell code allows for notifcations between VMCI: device driver implementaton. VMCI: event handling implementation. VMCI: handle array implementation. VMCI: queue pairs implementation. VMCI: resource object implementation. VMCI: routing implementation. VMCI: guest side driver implementa...

...lar VMCI Sockets, please refer to the VMCI Socket Programming Guide available at https://www.vmware.com/support/developer/vmci-sdk/. --- George Zhang (12): VMCI: context implementation. VMCI: datagram implementation. VMCI: doorbell implementation. VMCI doorbell code allows for notifcations between VMCI: device driver implementaton. VMCI: event handling implementation. VMCI: handle array implementation. VMCI: queue pairs implementation. VMCI: resource object implementation. VMCI: routing implementation. VMCI: guest side driver implementa...

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.