search for: notifi

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi, We've implemented a 'page-all' function for some of our customers, and we've noticed that on occasion the page-all will cause asterisk to crash (safe_asterisk then restarts it again). The particular customer has about 20 phones, and also has 5 Linksys 932 to monitor the state of these extensions. I'm not sure whether it is the page-all that causes the crash, or the

...E-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.02, addr 2> on usbus1 Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut because nut_enable is NO. Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO. Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO. Dec 10 21:40:20 nas6 notifier: nut...

...aults ) loads h264 files in vdpau mode instead of asserting ... But may be it will mess up things differently ..... I also run into this error: [ 5486.914351] nouveau 0000:01:00.0: disp: ERROR 1 [PUSHBUFFER_ERR] 02 [] chid 0 mthd 0000 data 00000400 [ 5488.914339] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5494.140509] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5496.144313] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5498.220935] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5500.232161] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5502.263648] nouveau 0000:01:00...

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

Nice! it seems to works. Later this evening when I'll be back to my home I'll try to unplug the power chord from my ups. Apr 3 14:08:11 archivio notifier: nut not running? (check > /var/db/nut/upsd.pid). > Apr 3 14:08:11 archivio notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Apr 3 14:08:11 archivio notifier: nut_upslog not running? (check > /var/db/nut/upslog.pid). > Apr 3 14:08:11 archivio notifier: nut n...

...------------------------------- User Columns (0.041488) SHOW FIELDS FROM `users` User Load (0.001544) SELECT * FROM `users` WHERE (`users`.`nickname` = ''jamal'') LIMIT 1 SQL (0.000373) BEGIN SQL (0.001843) SHOW TABLES User::Notify Load (0.001113) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.001009) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.000996) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.000862) SELECT * FR...

...s transport layer to pass on the lost device info to virtio's backend driver virtio_blk. Heinz Graalfs (3): virtio: add notify() callback to virtio_driver virtio_blk: add virtblk_notify() as virtio_driver's notify() callback virtio_ccw: invoke virtio_driver's notify() on CIO_GONE notification drivers/block/virtio_blk.c | 14 ++++++++++++++ drivers/s390/kvm/virtio_ccw.c | 14 ++++++++++++-- drivers/virtio/virtio.c | 8 ++++++++ include/linux/virtio.h | 10 ++++++++++ 4 files changed, 44 insertions(+), 2 deletions(-) -- 1.8.3.1

...s transport layer to pass on the lost device info to virtio's backend driver virtio_blk. Heinz Graalfs (3): virtio: add notify() callback to virtio_driver virtio_blk: add virtblk_notify() as virtio_driver's notify() callback virtio_ccw: invoke virtio_driver's notify() on CIO_GONE notification drivers/block/virtio_blk.c | 14 ++++++++++++++ drivers/s390/kvm/virtio_ccw.c | 14 ++++++++++++-- drivers/virtio/virtio.c | 8 ++++++++ include/linux/virtio.h | 10 ++++++++++ 4 files changed, 44 insertions(+), 2 deletions(-) -- 1.8.3.1

Update nouveau to only use the mmu interval notifiers. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- drivers/gpu/drm/nouveau/nouveau_svm.c | 313 +++++++++++++++++--------- 1 file changed, 201 insertions(+), 112 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_svm.c b/drivers/gpu/drm/nouveau/nouveau_svm.c index df9bf...

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0,

From: Jason Gunthorpe <jgg at mellanox.com> Remove the hmm_mirror object and use the mmu_range_notifier API instead for the range, and use the normal mmu_notifier API for the general invalidation callback. While here re-organize the pagefault path so the locking pattern is clear. nouveau is the only driver that uses a temporary range object and instead forwards nearly every invalidation range dir...

...t;> r262572+ >> 38751c8: Thu Mar 20 21:13:02 PDT 2014 root at build.ixsystems.com: >> /tank/home/jk >> >> h/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/ >> src/sys/FREENAS.amd64 amd64 > > > > Apr 3 09:05:36 archivio notifier: nut not running? (check >> /var/db/nut/upsd.pid). >> Apr 3 09:05:36 archivio notifier: nut_upsmon not running? (check >> /var/db/nut/upsmon.pid). >> Apr 3 09:05:36 archivio notifier: nut_upslog not running? (check >> /var/db/nut/upslog.pid). >> Apr 3 09:05:36...

...t queueing for lost devices appropriate settings in the block layer should be made. Exploiting System z's CIO notify handler callback, and adding a corresponding new virtio_driver notify() handler to 'inform' the block layer, solve this task. v1->v2 changes: - add include of linux/notifier.h (I also added it to the 3rd patch) - get queue lock in order to be able to use safe queue_flag_set() functions in virtblk_notify() handler Patch 1 adds an optional notify() callback to virtio_driver. Patch 2 adds a new notify() callback for the virtio_blk driver. When called for a lost d...

...t queueing for lost devices appropriate settings in the block layer should be made. Exploiting System z's CIO notify handler callback, and adding a corresponding new virtio_driver notify() handler to 'inform' the block layer, solve this task. v1->v2 changes: - add include of linux/notifier.h (I also added it to the 3rd patch) - get queue lock in order to be able to use safe queue_flag_set() functions in virtblk_notify() handler Patch 1 adds an optional notify() callback to virtio_driver. Patch 2 adds a new notify() callback for the virtio_blk driver. When called for a lost d...

Hi, I have a query regarding running a manual update of nsd via: # nsdc update My NSD server is accepting notifications from two servers. From my nsd.conf: # master 1 allow-notify: X.X.X.X NOKEY request-xfr: AXFR X.X.X.X NOKEY # master 2 allow-notify: Y.Y.Y.Y NOKEY request-xfr: AXFR Y.Y.Y.Y NOKEY Are both servers sequentially queried each time the update is ru...

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting NUT; Mar 31 09:11:15...

...;# Move spam to spam folderif exists "X-Spam-Flag" { fileinto "spam"; # Stop here so that we do not reply on spams stop;}notify :method "mailto:phxxx at xxp.com":message "Vous avez recu un message sur votre adresse"; # Don't send any further notifications stop;What's wrong? I've tried example from http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-12.txt but they are not working.Thanks for helpPhilippe _________________________________________________________________ Invite your mail contacts to join your friends l...

...9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu Mar 20 21:13:02 PDT 2014 root at build.ixsystems.com:/tank/home/jk > h/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/ > src/sys/FREENAS.amd64 amd64 > > > Apr 3 09:05:36 archivio notifier: nut not running? (check /var/db/nut/upsd.pid). > Apr 3 09:05:36 archivio notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). > Apr 3 09:05:36 archivio notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). > Apr 3 09:05:36 archivio notifier: nut not running? (ch...