opendkim-genzone(8) [debian man page]

opendkim-genzone(8)					      System Manager's Manual					       opendkim-genzone(8)

NAME

       opendkim-genzone - DKIM public key zone file generation tool

SYNOPSIS

       opendkim-genzone  [-C  address]	[-d  domain] [-D] [-E secs] [-N ns[,...]]  [-o file] [-r secs] [-R secs] [-S] [-t secs] [-T secs] [-v] [-x
       conffile] [dataset]

DESCRIPTION

       opendkim-genzone generates a file suitable for use with named(8) to publish a set of public keys.

       The dataset parameter should specify a set of data as described in the opendkim(8) man page.  It can currently refer to flat files, Sleepy-
       cat  databases,	comma-separated  lists, LDAP directories or SQL databases.  The dataset may be omitted if a configuration file (via the -x
       command line flag) is specified referring to a configuration file that sets a KeyTable parameter, in which case that value will be used.

       The database contents should be formatted as described for the KeyTable parameter, described in the opendkim.conf(5) man page.

OPTIONS

       -C contact
	      Uses contact as the contact information to be used when an SOA record is generated (see -S below).  If not specified, the userid	of
	      the executing user and the local hostname will be used; if the executing user can't be determined, "hostmaster" will be used.

       -d domain
	      Restricts output to those records for which the domain field is the specified domain.

       -D     Adds a "._domainkey" suffix to selector names in the zone file.

       -E secs
	      When generating an SOA record (see -S below), use secs as the default record expiration time.  The default is 604800.

       -N nslist
	      Specifies a comma-separated list of nameservers, which will be output in NS records before the TXT records.  The first nameserver in
	      this list will also be used in the SOA record (if -S is also specified) as the authority hostname.

       -o file
	      Sends output to the named file rather than standard output.

       -r secs
	      When generating an SOA record (see -S below), use secs as the zone refresh time.	The default is 10800.

       -R secs
	      When generating an SOA record (see -S below), use secs as the zone retry time.  The default is 1800.

       -S     Asks for an SOA record to be generated at the top of the output.	The content of this output can be controlled using the -E, -r, -R,
	      -T options.  The serial number will be generated based on the current time of day.

       -t ttl Puts a TTL (time-to-live) value of ttl on all records output.  The units are in seconds.

       -T secs
	      When generating an SOA record (see -S below), use secs as the default record TTL time.  The default is 86400.

       -v     Increases the verbosity of debugging output written to standard error.

       -x conffile
	      Names  an  opendkim.conf(5)  file  to  be  read for LDAP-specific parameters when an LDAP dataset is given on the command line.  Not
	      required for other dataset types.  The default is /etc/opendkim.conf.

VERSION

       This man page covers the version of opendkim-genzone that shipped with version 2.6.8 of OpenDKIM.

COPYRIGHT

       Copyright (c) 2010, 2012, The OpenDKIM Project.	All rights reserved.

SEE ALSO

       opendkim(8), opendkim.conf(5)

							       The OpenDKIM Project					       opendkim-genzone(8)

PX_INSERT_RECORD(3)													       PX_INSERT_RECORD(3)

px_insert_record - Inserts record into paradox database

SYNOPSIS

       int px_insert_record (resource  $pxdoc, array  $data)

DESCRIPTION

	Inserts  a  new  record  into  the database. The record is not necessarily inserted at the end of the database, but may be inserted at any
       position depending on where the first free slot is found.

	The record data is passed as an array of field values. The elements in the array must correspond to the fields in  the	database.  If  the
       array has less elements than fields in the database, the remaining fields will be set to null.

	Most  field values can be passed as its equivalent php type e.g. a long value is used for fields of type PX_FIELD_LONG, PX_FIELD_SHORT and
       PX_FIELD_AUTOINC, a double values is used for fields of type PX_FIELD_CURRENCY and PX_FIELD_NUMBER. Field values for blob and alpha  fields
       are passed as strings.

	Fields	of type PX_FIELD_TIME and PX_FIELD_DATE both require a long value. In the first case this is the number of milliseconds since mid-
       night. In the second case this is the number of days since 1.1.0000. Below there are two examples to convert the current date or  timestamp
       into a value suitable for one of paradox's date/time fields.

       Note

	       This function is only available if pxlib >= 0.6.0 is used.

PARAMETERS

	      o $pxdoc
		- Resource identifier of the paradox database as returned by px_new(3).

	      o $data
		- Associated or indexed array containing the field values as e.g. returned by px_retrieve_record(3).

RETURN VALUES

	Returns FALSE on failure or the record number in case of success.

EXAMPLES

       Example #1

	      Set the date/time fields in a paradox database to the current date/time

	      <?php
	      $px = px_new();
	      $fp = fopen("test.db", "w+");
	      px_create_fp($px, $fp, array(array("timestamp", "@"), array("time", "T"), array("date", "D")));

	      $curdate = getdate();
	      $jd = gregoriantojd($curdate["mon"], $curdate["mday"], $curdate["year"]);
	      $days = $jd - 1721425; /* Number of days between 1.1.4714 b.c. and 1.1.0000 */
	      $secs = $curdate["hours"]*3600 + $curdate["minutes"]*60 + $curdate["seconds"];
	      px_insert_record($px, array($days*86400000.0 + $secs*1000.0, $secs*1000.0, $days));

	      $curtimestamp = microtime(true);
	      $days = (int) ($curtimestamp/86400);
	      $secs = $curtimestamp - ($days * 86400.0);
	      $days += 2440588; /* Number of days between 1.1.4714 b.c. and 1.1.1970 */
	      $days -= 1721425; /* Number of days between 1.1.4714 b.c. and 1.1.0000 */
	      px_insert_record($px, array($days*86400000.0 + $secs*1000.0, $secs*1000.0, $days));
	      for($i=0; $i<2; $i++) {
		  $rec = px_retrieve_record($px, $i);
		  echo px_timestamp2string($px, $rec["timestamp"], "n/d/Y H:i:s")."
";
		  echo px_date2string($px, $rec["date"], "n/d/Y")."
";
	      }
	      px_close($px);
	      px_delete($px);
	      ?>

	      The above example will output:

	      2/21/2006 21:42:30
	      2/21/2006
	      2/21/2006 20:42:30
	      2/21/2006

	The  Julian  day  count  as  passed  to  jdtogregorian(3) has a different base of 1.1.4714 b.c. and must therefore be calculated by adding
       1721425 to the day count used in the paradox file. Turning the day count into a timestamp is easily done by multiplying with 86400000.0	to
       obtain milli seconds.

SEE ALSO

       px_update_record(3)

PHP Documentation Group 												       PX_INSERT_RECORD(3)