GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  DKP (8)

NAME

dkp - Diablo program to manage DKP databases

CONTENTS

Synopsis
Description
General KP database maintenance

SYNOPSIS

dkp [-x] [-r] [-w] [-d] [-s] [-t] filename [key [tok=data]] [ < input ]

DESCRIPTION

DKP manages KP databases. Currently Diablo has only one KP database, the active file, called dactive.kp. issues a command to the parent diablo server. The command allows a key and optional tok=data (for writes) to be specified on the command line. If no key/data is specified, DKP takes key or key tok=data lines from the standard input. The data may not contain spaces, tabs, or newlines.

-x - cause the specified key (or keys on stdin, one per line) to be deleted from the database.

-r - lookup the specified key and print the record.

-w - write the specified tok=data to the database for the record specified by the given key. A record can have multiple tokens associated with it but DKP currently accepts only one at a time.

-d - Turn on debugging

-s - Force the KP database to be sorted in-place. This option is not normally necessary, but is useful as a safety precaution if you believe the database has been manually edited.

-t - Trim the KP database, removing dead records. This will only work if no other processes have the specified KP database open. It should be done on dactive.kp once a month. If you are generating a fresh dactive.kp from some other source, always run dkp -t on it to clear out all the temporary junk. filename - specify the name of the KP database file. This is a required parameter.

General KP database maintenance

KP databases can be manually edited, but only if there are no active references. If you have an editor capable of performing an flock, such as nvi, your editor will warn you if other processes have active references to the database because the database code maintains several locks on the database file.

KP databases can be replaced by generating a new copy and renaming it over the old, but if active references exist they will continue to work on the old, possibly until they close. Since the diablo reader code leaves active opens on the dactive.kp database, you should use only the dkp program to fix it unless you shut down the reader entirely.

KP databases handle changes in record size by marking the old record as deleted (a ’-’ instead of a ’+’) and appending a new record. This means that garbage can collect in the database file. The garbage can be pruned safely with ’dkp -t’. DO NOT USE A GREP/RENAME TO PRUNE A KP DATABASE!

Diablo gives instructions on how to prune its various KP databases by example, usually in the adm/ or samples/ directory.

SEE ALSO

diablo(8), dicmd(8), didump(8), diload(8), dnewslink(8), doutq(8), dexpire(8), dexpireover(8), diconvhist(8), dilookup(8), dspoolout(8), dkp(8), dpath(8), diablo-kp(5), diablo-files(5)

Search for    or go to Top of page |  Section 8 |  Main Index


DKP (8) -->

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.