Home
last modified time | relevance | path

Searched refs:notifications (Results 1 – 25 of 34) sorted by relevance

12

/openbsd/src/sbin/isakmpd/
DQUESTIONS16 result in error notifications which potentially result in SA tear-down?
17 Maybe should notifications never be issued for erroneous packets which
19 notifications?
DTO-DO100 * Handle notifications showing the peer did not want to continue this exchange.
/openbsd/src/gnu/usr.bin/binutils/gdb/
Dobserver.sh92 /* ${event} notifications. */
105 /* ${event} notifications. */
/openbsd/src/gnu/usr.bin/binutils/gdb/doc/
Dobserver.texi11 notifications, the observer attaches a callback to the subject.
17 management routines for all possible notifications.
39 Observer notifications can be traced using the command @samp{set debug
Dgdbint.texinfo702 @cindex notifications about changes in internals
717 interface when adding new notifications.
1438 As an observer (using @file{gdb-events}) receiving notifications from
1492 the processing of any event notifications until after @code{libgdb} has
/openbsd/src/etc/
Dcrontab13 # send log file notifications, if necessary
/openbsd/src/gnu/llvm/llvm/docs/
DHowToAddABuilder.rst135 notifications on build failure; for this you'll need to add an
153 up with the build queue. No notifications will be sent, so you can
158 buildmaster to enable developer notifications. Please email `Galina
251 This makes the build failure notifications markedly less actionable, and
/openbsd/src/sys/dev/pci/drm/radeon/
Dradeon_acpi.c236 radeon_atif_parse_notification(&atif->notifications, output.notification_mask); in radeon_atif_verify_interface()
734 if (atif->notifications.brightness_change) { in radeon_acpi_init()
Dradeon.h2290 struct radeon_atif_notifications notifications; member
/openbsd/src/sys/dev/pci/drm/amd/amdgpu/
Damdgpu_acpi.c109 struct amdgpu_atif_notifications notifications; member
272 amdgpu_atif_parse_notification(&atif->notifications, output.notification_mask); in amdgpu_atif_verify_interface()
1255 if (atif->notifications.brightness_change) { in amdgpu_acpi_init()
/openbsd/src/share/snmp/
DVM-MIB.txt1149 notifications per virtual machine. Changes to this
1160 notifications per set of virtual machines. Changes to
1172 notifications."
1476 "Support for per-VM notifications is optional. If not
1485 "Support for bulk notifications is optional. If not
1638 "A collection of notifications for per-VM notification
1668 "A collection of notifications for bulk notification of
DSNMPv2-CONF.txt284 -- only "not-implemented" for notifications
DSNMPv2-SMI.txt300 -- definitions for notifications
DSNMPv2-MIB.txt382 -- information for notifications
588 "The basic notifications implemented by an SNMP entity
DBRIDGE-MIB.txt1336 "Group of objects describing notifications (traps)."
DIF-MIB.txt1356 "The notifications which indicate specific changes in the
/openbsd/src/usr.sbin/nsd/doc/
DREADME304 Access control lists are needed for zone transfer and notifications.
436 when needed. When primary zones are updated and reloaded notifications
443 NSD will send notifications to slave zones if a master zone is updated.
449 notifications to the slave servers configured in 'notify:' statements.
567 # allow only notifications that are signed
611 zones, NSD will issue notifications to all configured 'notify:' targets.
/openbsd/src/usr.sbin/snmpd/
Dmib.y629 notificationspart : NOTIFICATIONS '{' notifications '}'
632 notifications : notification
633 | notification ',' notifications
1593 mib_notificationgroup(const char *name, void *notifications, enum status status, in mib_notificationgroup() argument
/openbsd/src/gnu/usr.bin/cvs/doc/
Dcvs.info-4118 flexible way of giving notifications to various users, which requires
718 You can tell CVS that you want to receive notifications about
778 receive notifications on the server machine. One could of course write
779 a `notify' script which directed notifications elsewhere, but to make
815 `commit'ted. If the user does not wish to receive notifications,
847 the server; the notifications will be sent upon the next successful CVS
Dcvsclient.info-2364 requests. Even if a client is capable of deferring notifications,
Dcvs.info-11087 This file stores notifications (for example, for `edit' or
Dcvs.texinfo1657 This file stores notifications (for example, for
5309 notifications to various users, which requires less in
6310 notifications about various actions taken on a file.
6395 way, users receive notifications on the server machine.
6397 directed notifications elsewhere, but to make this
6461 receive notifications, she should specify @code{-a none}.
6513 server; the notifications will be sent upon the next
/openbsd/src/usr.bin/ssh/
DPROTOCOL.mux287 XXX server->client error/warning notifications
/openbsd/src/gnu/usr.bin/perl/pod/
Dperlsecpolicy.pod368 =head3 Pre-release notifications
Dperlhack.pod191 the tree, see recent commits, subscribe to repository notifications,

12