| /freebsd/crypto/krb5/doc/ |
| H A D | iprop-notes.txt | 8 the replica side stopping all the incremental propagation stuff and
11 resumes incremental propagation.
18 recovery or other cases without doing a full propagation or restoring
34 cascade propagation model where A sends to B which sends to C, perhaps
40 The propagation of changes does not happen in real time. It's not a
61 Why are different principal names used, when incremental propagation
69 The incremental propagation protocol requires an ACL entry on the
74 out the database and attempt a full propagation.
87 full propagation only. Doing incremental propagation over IPv6 will
|
| /freebsd/crypto/krb5/src/man/ |
| H A D | kpropd.man | 51 propagation is enabled, it periodically requests incremental updates
63 Where incremental propagation is not used, kpropd is commonly invoked
80 propagation. Starting in release 1.11, kpropd automatically detects
86 Incremental propagation may be enabled with the \fBiprop_enable\fP
87 variable in kdc.conf(5)\&. If incremental propagation is
92 the update entry log on the replica KDC. If incremental propagation
156 will allow Kerberos database propagation via kprop(8)\&.
|
| H A D | kadmind.man | 77 kadmind can be configured for incremental database propagation.
78 Incremental propagation allows replica KDC servers to receive
82 propagation requires the principal \fBkiprop/PRIMARY\e@REALM\fP (where
105 incremental propagation polling requests. This option can be used
106 to set up a hierarchical propagation topology where a replica KDC
|
| /freebsd/crypto/krb5/doc/html/_sources/admin/admin_commands/ |
| H A D | kpropd.rst.txt | 27 propagation is enabled, it periodically requests incremental updates
39 Where incremental propagation is not used, kpropd is commonly invoked
48 propagation. Starting in release 1.11, kpropd automatically detects
54 Incremental propagation may be enabled with the **iprop_enable**
55 variable in :ref:`kdc.conf(5)`. If incremental propagation is
60 the update entry log on the replica KDC. If incremental propagation
130 will allow Kerberos database propagation via :ref:`kprop(8)`.
|
| H A D | kadmind.rst.txt | 51 kadmind can be configured for incremental database propagation.
52 Incremental propagation allows replica KDC servers to receive
56 propagation requires the principal ``kiprop/PRIMARY\@REALM`` (where
81 incremental propagation polling requests. This option can be used
82 to set up a hierarchical propagation topology where a replica KDC
|
| /freebsd/crypto/krb5/doc/admin/admin_commands/ |
| H A D | kpropd.rst | 27 propagation is enabled, it periodically requests incremental updates
39 Where incremental propagation is not used, kpropd is commonly invoked
48 propagation. Starting in release 1.11, kpropd automatically detects
54 Incremental propagation may be enabled with the **iprop_enable**
55 variable in :ref:`kdc.conf(5)`. If incremental propagation is
60 the update entry log on the replica KDC. If incremental propagation
130 will allow Kerberos database propagation via :ref:`kprop(8)`.
|
| H A D | kadmind.rst | 51 kadmind can be configured for incremental database propagation.
52 Incremental propagation allows replica KDC servers to receive
56 propagation requires the principal ``kiprop/PRIMARY\@REALM`` (where
81 incremental propagation polling requests. This option can be used
82 to set up a hierarchical propagation topology where a replica KDC
|
| /freebsd/contrib/ntp/clockstuff/ |
| H A D | propdelay.c | 2 * propdelay - compute propagation delays
10 * This can be used to get a rough idea of the HF propagation delay
38 * to find the propagation delays to WWV and WWVH (from CHU in this
199 "summer propagation, "); in main()
201 "winter propagation, "); in main()
215 "WWV summer propagation, "); in main()
217 "WWV winter propagation, "); in main()
229 "WWVH summer propagation, "); in main()
231 "WWVH winter propagation, "); in main()
242 "CHU summer propagation, "); in main()
[all …]
|
| /freebsd/share/doc/psd/18.gprof/ |
| H A D | postp.me | 41 Time propagation is performed from the leaves of the
97 Time propagation within strongly connected
106 but do not participate in time propagation.
107 Thus the simple equation for time propagation
152 Since cycles often have a significant effect on time propagation,
180 Thus they are never responsible for any time propagation.
|
| /freebsd/contrib/llvm-project/llvm/lib/CodeGen/ |
| H A D | RegUsageInfoPropagate.cpp | 1 //=--- RegUsageInfoPropagate.cpp - Register Usage Informartion Propagation --=//
37 #define RUIP_NAME "Register Usage Information Propagation"
76 INITIALIZE_PASS_BEGIN(RegUsageInfoPropagation, "reg-usage-propagation",
79 INITIALIZE_PASS_END(RegUsageInfoPropagation, "reg-usage-propagation",
118 << "Call Instruction Before Register Usage Info Propagation : \n" in runOnMachineFunction()
141 << "Call Instruction After Register Usage Info Propagation : \n" in runOnMachineFunction()
|
| /freebsd/crypto/krb5/doc/html/_sources/admin/ |
| H A D | database.rst.txt | 271 waiting until the next scheduled propagation. If you do not have
487 Incremental database propagation
495 primary KDC to the replica KDCs. The incremental propagation support
498 With incremental propagation enabled, all programs on the primary KDC
506 Incremental propagation uses the following entries in the per-realm
510 …oolean* If *true*, then incremental propagation is enabled, and (as noted below) normal kpro…
513 … *integer* Specifies the port number to be used for incremental propagation. This is requir…
514 …t *integer* Specifies the number of seconds to wait for a full propagation to complete. Th…
531 incremental propagation is enabled, it will connect to the kadmind on
534 The normal kprop mechanism is disabled by the incremental propagation
[all …]
|
| H A D | lockout.rst.txt | 101 traditional :ref:`kprop(8)` or incremental propagation. Because of
110 KDCs during the next propagation. Propagation of an administrative
115 incremental propagation, such as the LDAP KDB module with multi-master
|
| H A D | realm_config.rst.txt | 250 Database propagation
255 deciding how frequently the propagation should happen, you will need
256 to balance the amount of time the propagation takes against the
260 If the propagation time is longer than this maximum reasonable time
263 cut down on your propagation delay by performing the propagation in
|
| H A D | install_kdc.rst.txt | 366 Database propagation copies the contents of the primary's database,
408 krb5_prop 754/tcp # Kerberos replica propagation
413 required when incremental propagation is enabled.
415 Now that the replica KDC is able to accept database propagation,
437 Database propagation to kerberos-1.mit.edu: SUCCEEDED
473 Propagation failed?
517 #. Run your database propagation script manually, to ensure that the
531 Incremental database propagation
535 set up incremental propagation to replica KDCs. See
|
| /freebsd/crypto/krb5/doc/admin/ |
| H A D | database.rst | 271 waiting until the next scheduled propagation. If you do not have
487 Incremental database propagation
495 primary KDC to the replica KDCs. The incremental propagation support
498 With incremental propagation enabled, all programs on the primary KDC
506 Incremental propagation uses the following entries in the per-realm
510 …oolean* If *true*, then incremental propagation is enabled, and (as noted below) normal kpro…
513 … *integer* Specifies the port number to be used for incremental propagation. This is requir…
514 …t *integer* Specifies the number of seconds to wait for a full propagation to complete. Th…
531 incremental propagation is enabled, it will connect to the kadmind on
534 The normal kprop mechanism is disabled by the incremental propagation
[all …]
|
| H A D | lockout.rst | 101 traditional :ref:`kprop(8)` or incremental propagation. Because of
110 KDCs during the next propagation. Propagation of an administrative
115 incremental propagation, such as the LDAP KDB module with multi-master
|
| H A D | realm_config.rst | 250 Database propagation
255 deciding how frequently the propagation should happen, you will need
256 to balance the amount of time the propagation takes against the
260 If the propagation time is longer than this maximum reasonable time
263 cut down on your propagation delay by performing the propagation in
|
| H A D | install_kdc.rst | 366 Database propagation copies the contents of the primary's database,
408 krb5_prop 754/tcp # Kerberos replica propagation
413 required when incremental propagation is enabled.
415 Now that the replica KDC is able to accept database propagation,
437 Database propagation to kerberos-1.mit.edu: SUCCEEDED
473 Propagation failed?
517 #. Run your database propagation script manually, to ensure that the
531 Incremental database propagation
535 set up incremental propagation to replica KDCs. See
|
| /freebsd/usr.bin/gprof/ |
| H A D | gprof.callg | 55 the propagation fraction.
77 propagation fraction for this child.
81 propagation fraction.
94 the propagated times and propagation denominator
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/Scalar/ |
| H A D | SCCP.h | 1 //===- SCCP.cpp - Sparse Conditional Constant Propagation -------*- C++ -*-===//
10 // This file implements sparse conditional constant propagation and merging:
28 /// This pass performs function-level constant propagation and merging.
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/IPO/ |
| H A D | SCCP.h | 1 //===- SCCP.h - Sparse Conditional Constant Propagation ---------*- C++ -*-===//
10 // propagation and merging.
47 /// Pass to perform interprocedural constant propagation.
|
| /freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Checkers/ |
| H A D | GenericTaintChecker.cpp | 9 // This checker defines the attack surface for generic taint propagation.
243 /// A struct used to specify taint propagation rules for a function.
254 /// Arguments which can participate in taint propagation. If any of the
306 /// Functions for custom taintedness propagation.
330 struct Propagation : Common { struct
337 std::vector<Propagation> Propagations;
377 TaintConfiguration::Propagation &&P,
421 LLVM_YAML_IS_SEQUENCE_VECTOR(TaintConfiguration::Propagation)
449 template <> struct MappingTraits<TaintConfiguration::Propagation> {
450 static void mapping(IO &IO, TaintConfiguration::Propagation &Propagation) { in mapping()
[all …]
|
| /freebsd/contrib/ntp/html/drivers/ |
| H A D | driver36.html | 23 …OM receivers, the receiver can be tuned automatically by the driver as propagation conditions chan…
25 …try. In Newark DE, 2479 km from the transmitter, the predicted two-hop propagation delay varies fr…
26 …th 0.4 ms jitter. The long-term mean offset varies up to 0.3 ms due to propagation path geometry v…
48 …ay be available at different times or even at the same time. Since the propagation times from eith…
52 …propagation medium. Conventional wisdom is that manual synchronization via oscilloscope and HF med…
56 <p>The predicted propagation delay from the WWV transmitter at Boulder, CO, to the receiver at Newa…
61 …i>f</i> for WWVH, where <i>f</i> is the frequency in megahertz. If the propagation delays have bee…
65 …ovisions to automatically tune the radio in response to changing radio propagation conditions thro…
67 …es are probed in a five-minute rotation to build a database of current propagation conditions for …
74 …ful for evaluating the performance of the algorithms, as well as radio propagation conditions in g…
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/Utils/ |
| H A D | SampleProfileLoaderBaseImpl.h | 277 /// Set of visited blocks during propagation.
280 /// Set of visited edges during propagation.
624 // during the propagation phase. Right now, we just want to
961 // The first propagation propagates BB counts from annotated BBs to unknown
962 // BBs. The 2nd propagation pass resets edges weights, and use all BB
970 // The 3rd propagation pass allows adjust annotated BB weights that are
990 /// propagation heuristic. Propagation proceeds in 3 phases:
1003 /// 3- Propagation of block weights into edges. This uses a simple
1004 /// propagation heuristic. The following rules are applied to every
1021 /// Since this propagation is not guaranteed to finalize for every CFG, we
[all …]
|
| /freebsd/crypto/heimdal/etc/ |
| H A D | services.append | 20 krb_prop 754/tcp hprop # Kerberos slave propagation
28 iprop 2121/tcp # incremental propagation
|