summaryrefslogtreecommitdiffstats
path: root/testsuite/systemtap.base/div0.stp
blob: b2694e58fae4bda6b6e5281b3b1d195725bcbe4a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
/*
 * div.stp0
 *
 * Check the systemtap divide by 0 does not kill the machine
 *	
 * Note: Error messages are written to stderr. That means it is
 * possible that if a printf is followed by something that 
 * generates an error, the error will get displayed before the printf.
 * That is why both print's are in the begin probe.
 * 
 */

global x3
global x1
global x2

probe begin
{
	print("systemtap starting probe\n")
	print("systemtap ending probe\n")
	x1 = 56088; x2 = 0;
}

probe end
{
	x3 = x1 / x2
	/* this part does not get executed */
	if (x3 != 456 )
		print("systemtap test failure\n")
	else
		print("systemtap test failure\n")
}
n64' href='#n64'>64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85
.. _kpropd:

kpropd(8)
===========


SYNOPSIS
----------

***kpropd***
          [ **-r** *realm* ] 
          [ **-f** *slave_dumpfile* ] 
          [ **-F** *principal_database* ] 
          [ **-p** *kdb5_util_prog* ] 
          [ **-d** ] 
          [ **-S** ] 
          [ **-P** *port* ]

DESCRIPTION
-------------

The *kpropd* command runs on the slave KDC server.  
It listens for update requests made by the :ref:`kprop` program, and periodically requests incremental updates from the master KDC.

When the slave receives a kprop request from the master, *kpropd* accepts the dumped KDC database and places it in a file, 
and then runs kdb5_util(8) to load the dumped database into the active database which is used by :ref:`krb5kdc`.  
Thus, the master Kerberos server can use :ref:`kprop` to propagate its database to the slave slavers.  
Upon a successful download of the KDC database file, the slave Kerberos server will have an up-to-date KDC database.

Normally, *kpropd* is invoked out of inetd(8).  This is done by adding a line to the *inetd.conf* file which looks like this::

       kprop     stream    tcp  nowait    root /usr/local/sbin/kpropd   kpropd

However, *kpropd* can also run as a standalone daemon, if the *-S* option is turned on.  
This is done for debugging purposes, or if for some reason the system administrator just doesn't want to run it out of inetd(8).

When the slave periodically requests incremental updates, *kpropd* updates its *principal.ulog* file with any updates from the master.  
:ref:`kproplog` can be used to view a summary of the update entry log on the slave KDC.  
Incremental propagation is not enabled by default; it can be enabled using the *iprop_enable* and *iprop_slave_poll* settings in :ref:`kdc.conf`).  
The principal "kiprop/slavehostname@REALM" (where "slavehostname" is the name of the slave KDC host, 
and "REALM" is the name of the Kerberos realm) must be present in the slave's keytab file.

OPTIONS
--------

       **-r** *realm*
              Specifies the realm of the master server; by default the realm returned by krb5_default_local_realm(3) is used.

       **-f** *file*
              Specifies the filename where the dumped principal database file is to be stored; by default the dumped database file is *KPROPD_DEFAULT_FILE*
              (normally /usr/local/var/krb5kdc/from_master).

       **-p**
              Allows the user to specify the pathname to the kdb5_util(8) program; by default the pathname used is *KPROPD_DEFAULT_KDB5_UTIL*
              (normally /usr/local/sbin/kdb5_util).

       **-S**     
              Turn on standalone mode.  Normally, *kpropd* is invoked out of inetd(8) so it expects a network connection to be passed to it from inetd(8).
              If the *-S* option is specified, *kpropd* will put itself into the background, and wait for connections to the  *KPROP_SERVICE* port  
              (normally *krb5_prop*).

       **-d**     
              Turn on debug mode.  In this mode, if the *-S* option is selected, *kpropd* will not detach itself from the current job
              and run in the background.  Instead, it will run in the foreground and print out debugging messages during the database propagation.

       **-P**     
               Allow for an alternate port number for *kpropd* to listen on. This is only useful if the program is run in standalone mode.

       **-a**     
              Allows the user to specify the path to the *kpropd.acl* file; by default the path used is *KPROPD_ACL_FILE*   
              (normally /usr/local/var/krb5kdc/kpropd.acl).

FILES
---------

*kpropd.acl*  
            Access file for *kpropd*; the default location is KPROPD_ACL_FILE (normally /usr/local/var/krb5kdc/kpropd.acl).  
            Each entry is a line containing the principal of a host from which the local machine will allow Kerberos database propagation via :ref:`kprop`.

SEE ALSO
----------

kprop(8), kdb5_util(8), krb5kdc(8), inetd(8)