#############################################################################
# 
# %I% %D%
# 
# This is the RIPE database software main configuration file.
# Almost all tools that manage the databases use some parts of this
# config file, most of them do not use everything.
#
#############################################################################
# 
# Alter the pathnames below for your local environment
#
# NOTE THIS IS THE CURRENT PRODUCTION RIPE DATABASE CONFIG
# ALL OPTIONS THAT ARE SPECIFIC FOR THE RIPE NCC SETUP ARE COMMENTED OUT
#############################################################################

# Run database sw in test mode?  Testmode will cause ALL mail acks and other
# mail messages to be send to DEFMAIL defined further below.

TESTMODE	0

# file to keep people that can make entries using the update daemon
# not in distribution yet. In fact, it has not even been written ;-)
# It is a good idea though.

# AUTHFILE	/nccfs3/dbase-beta/conf.auth

# help file for "whois help"

HELP	/nccfs3/dbase/etc/db-help

# default database to do lookups in

DEFLOOK	RIPE

# if all databases are selected

ALLLOOK	RIPE
#ALLLOOK	RIPE INTERNIC ALTERNET NCC-AS-LIST 

# Filenames associated with sources, more than one source can point to a file
# Make sure that all the databases you define below are available ...
# The optional 3rd argument SPLIT says that all object types live in seperate
# files, and the file name mentioned here is a basename for all these
# seperate files. The real files will have the two letter for the object
# they contain attached to them. A mix and match of SPLIT and non
# split databases works fine.

DBFILE	RIPE	/nccfs3/dbase/data/ripe/ripe.db		SPLIT
#DBFILE	MERIT	/nccfs3/dbase/data/nsf/nsf.db
#DBFILE	NIC	/nccfs3/dbase/data/nsf/nic.db
#DBFILE	INTERNIC	/nccfs3/dbase/data/internic/internic.db
#DBFILE	NCC-AS-LIST	/nccfs3/dbase/data/asn/asn.db
#DBFILE	ALTERNET	/nccfs3/dbase/data/alter/alter.db

# What sources can be updated ? Others will generate an error.
# Remove this is you run a secondary copy of the RIPE database

# CANUPD	RIPE

# whoisd query log file

QRYLOG	/nccfs3/dbase/etc/qrylog/qrylog

# Error log file (if something really goes wrong ...)

ERRLOG	/nccfs3/dbase/etc/errlog

# this is where an audit trail for deletes and other important
# database actions goes. Only one liners are syslogged. Maintainer
# should take care of rotating logs and the like.

AUDITLOG /nccfs3/dbase/etc/audit/auditlog

# authorization log (not yet used)
# AUTHLOG	/nccfs3/dbase-beta/etc/authlog

# this is where all update requests will be logged, this SHOULD be a
# directory, logged will be in file YYMMDD with EOF markers between
# messages

UPDLOG	/nccfs3/dbase/etc/updlog

# this is where all acknowledgements will be logged, this SHOULD be a
# directory, logged will be in file YYMMDD with EOF markers between
# messages

ACKLOG	/nccfs3/dbase/etc/acklog

# This is where the whoisd pid goes once started
# (default: /tmp/whoisd.pid)

PIDFILE	/nccfs3/dbase/etc/whoisd.pid

# This is the lock file basename for cleandb, to avoid rename/open race
# condition. The database name is appended to this basename, to create
# sperate lock files for all databases.
# (default: /tmp/CLEANDB.LOCK)

CLEANLOCK	/nccfs3/dbase/CLEANDB.LOCK

# TMPDIR is the tmp directory where various tools keep tmp files.
# Make sure you have enough disk space, the tools do not understand
# "disk full" messages and will do unexpected things.
# (default: /tmp)

TMPDIR	/nccfs3/dbase/tmp

# DEFMAIL is the mailbox used when no mail notifications or acknowledgements
# both as to and from address in various places.
# IT MUST NOT BE THE AUTOMATIC MAILBOX!!!!

DEFMAIL	ripe-dbm@ripe.net

# HUMAILBOX is a human looked at mailbox, used for forwarding
# special objects. IT MUST NOT BE THE AUTOMATIC MAILBOX!!!!
# It can be used in mail messges as explained in MAILTXT below.

HUMAILBOX	ripe-dbm@ripe.net

# What to display if no match was found

NOMATCH	No entries found for the selected source(s).
NOMATCH	
NOMATCH	If you would like to search on arbitrary strings,
NOMATCH	please use the WAIS server on wais.ripe.net or
NOMATCH	telnet to info.ripe.net for a WAIS client interface.
NOMATCH	The WAIS database name is ripe-database.
NOMATCH	This will only work for RIPE data.

# What to display if we got TOOMANY hits back

TOOMANY	The index search returned too many hits.
TOOMANY Please refine your search key.

# The list of valid attribute names themselves in short and long version
#
ATTR	ac	admin-c
ATTR    aa      as-name
ATTR	ad	address
ATTR    ae      as-exclude
ATTR	ai	as-in
ATTR	al	as-list
ATTR	an	aut-num
ATTR	am	as-macro
ATTR	ao	as-out
ATTR	as	aut-sys
ATTR    at      auth
ATTR	au	authority
ATTR	bg	bdry-gw
ATTR	bi	bis
ATTR	bl	bdrygw-l
ATTR	ch	changed
ATTR	cl	comm-list
ATTR	cm	community
ATTR	co	connect
ATTR	cy	country
ATTR	da	dom-name
ATTR	de	descr
ATTR	df	default
ATTR	di	dom-net
ATTR	dm	dom-in
ATTR	dn	domain
ATTR	do	dom-out
ATTR	dp	dom-prefix
ATTR    dt      upd-to
ATTR	em	e-mail
ATTR	fx	fax-no
ATTR	gd	guardian
ATTR	gw	gateway
ATTR    ho      hole
ATTR    if      ifaddr
ATTR	ii	ias-int
ATTR	in	inetnum
ATTR    ir      inet-rtr
ATTR    it      interas-in
ATTR    io      interas-out
ATTR    la      localas
ATTR	lo	location
ATTR	ma	maintainer
ATTR    mb      mnt-by
ATTR    mt      mntner
ATTR    mn      mnt-nfy
ATTR	na	netname
ATTR	nh	nic-hdl
ATTR	ni	nsf-in
ATTR	no	nsf-out
ATTR	ns	nserver
ATTR	ny	notify
ATTR	op	op-phone
ATTR	of	op-fax
ATTR	om	op-mail
ATTR    or      origin
ATTR    pe      peer
ATTR	ph	phone
ATTR	pn	person
ATTR	rl	routpr-l
ATTR	rm	remarks
ATTR	rp	rout-pr
ATTR    rt      route
ATTR	rz	rev-srv
ATTR	sd	sub-dom
ATTR	so	source
ATTR	tc	tech-c
ATTR    wd      withdrawn
ATTR	zc	zone-c

# TEMPORARY FOR MERIT, WILL DISSAPEAR IN APRIL 1995
ATTR	lr	local-route

# Attributes with u* short names are special!
# They all have hardcoded side effects, so do NOT change them
# unless you know what you are doing

ATTR	ua	authorise	# very special
ATTR	ud	delete		# delete operation
ATTR	ue	*ERROR*		# error attribute
ATTR	uo	override	# very special as well
ATTR	uw	WARNING		# warning attribute
#

# attribute aliases (because they appear so often!)
#
ATTA	ch	change
ATTA	fx	fax
ATTA	rm	remark
ATTA	ua	authorised
ATTA	ud	deleted
ATTA    aa      asname

# object alias for template mode
#
ALIAS	in	network
ALIAS	in	netnum

# The database objects in terms of their attributes
#
# ATSQ  - all defined attributes in this object, also defines print order
# MAND  - these attributes are mandatory
# OPT   - these attributes are optional
# MULT	- these attributes can appear more than once per object
# SORT	- sort order, single digit, lowest sorted first
# UNIQ	- these attributes define the unique key
# KEYS	- these attributes define all possible keys
# REC	- these attributes must be looked up if referenced
# OBS	- these attributes are obsoleted. When send in an update
#	  dbupdate will remove them and generate a warning.
#	  specially done for transitioning
#

# First, let's determine what objects are guarded, these can not be
# updated automatically, and will generate an error message. They
# need special magic to be included. And no, I'm not gonna tell what
# the magic is.

GRDOBJ	am an cm rt
# GRDOBJ am an cm rt mt

#	autonomous systems
#
OBJ     an      ATSQ    an aa de ai ao it io ae df gd ac tc
OBJ     an      ATSQ    rm ny mb ch so
OBJ     an      MAND    an de ac tc ch so
OBJ     an      OPT     aa ai ao it io ae df gd rm ny ma mb
OBJ     an      MULT    de ai ao it io ae df ac tc rm ch ny mb
OBJ     an      SORT    0
OBJ     an      UNIQ    an
OBJ     an      KEYS    an
OBJ     an      REC     ac tc


#	as macros
#
OBJ     am      ATSQ    am de al gd tc ac rm ny mb ch so
OBJ     am      MAND    am de al gd tc ac mb ch so
OBJ     am      OPT     rm ny
OBJ     am      MULT    de al tc ac rm ch ny mb
OBJ     am      SORT    8
OBJ     am      UNIQ    am
OBJ     am      KEYS    am
OBJ     am      REC     tc ac

#	boundary gateways - obsoleted 940906
#
# OBJ	bg	ATSQ	bg de lo au gd ac tc rm ny ma ch so
# OBJ	bg	MAND	ac au bg ch de gd lo so tc
# OBJ	bg	OPT	ny ma rm
# OBJ	bg	MULT	ac de lo tc ch ny
# OBJ	bg	SORT	1
# OBJ	bg	UNIQ	bg
# OBJ	bg	KEYS	bg
# OBJ	bg	REC	ac tc

#	community
#
OBJ	cm	ATSQ	cm de au gd tc ac rm ny ma mb ch so
OBJ	cm	MAND	cm de au gd tc ac mb ch so
OBJ	cm	OPT	ny ma rm
OBJ	cm	MULT	de tc ac rm ch ny mb
OBJ	cm	SORT	6
OBJ	cm	UNIQ	cm
OBJ	cm	KEYS	cm
OBJ	cm	REC	ac tc
OBJ	cm	OBS	ma

#	domains
#
OBJ	dn	ATSQ	dn de ac tc zc ns sd di rm ny ma mb ch so
OBJ	dn	MAND	ac ch de dn so tc zc 
OBJ	dn	OPT	di ns rm sd  ny ma mb
OBJ	dn	MULT	ac ch de di ns rm sd tc zc ny mb
OBJ	dn	SORT	4
OBJ	dn	UNIQ	dn
OBJ	dn	KEYS	dn
OBJ	dn	REC	ac tc zc
OBJ	dn	OBS	ma

#	networks
#
OBJ	in	ATSQ	in na de cy ac tc co as cl ii ni no gw rz
OBJ	in	ATSQ	rm ny ma mb ch so
OBJ	in	MAND	ac ch cy de in na so tc
OBJ	in	OPT	as bl cl co ch gw ii ni no rl rm rz ny ma mb
OBJ	in	MULT	ac ch de ii rm rz tc ny mb
OBJ	in	SORT	5
OBJ	in	UNIQ	in
OBJ	in	KEYS	in na
OBJ	in	REC	ac tc
# OBJ	in	GRD	as cl
OBJ	in	OBS	bl rl ma

# Do not use the guarded stuff any more. It works like the previous versions
# but will be obsoleted shortly.

# GUARD	cl	/nccfs3/dbase/guarded/community	MULTIPLE
# GUARD	as	/nccfs3/dbase/guarded/as	SINGLE

# routing privilege /boundary gateway obsoleted 940906 mt
# Left in here to make sure they are all gone. Point to empty directory.

# GUARD	rl	/nccfs3/dbase/guarded/removed	MULTIPLE
# GUARD	bl	/nccfs3/dbase/guarded/removed	MULTIPLE

#	persons
#
OBJ	pn	ATSQ	pn ad ph fx em nh rm ny ma mb ch so
OBJ	pn	MAND	ad ch ph pn so
OBJ	pn	OPT	em fx nh rm ny ma mb
OBJ	pn	MULT	ad ch em fx ph rm ny mb
OBJ	pn	SORT	3
OBJ	pn	UNIQ	pn nh
OBJ	pn	KEYS	pn nh
OBJ	in	OBS	ma

#	routing privileges - obsoleted 940906 mt
#
# OBJ	rp	ATSQ	rp de au gd ac tc rm ny ma ch so
# OBJ	rp	MAND	ac au ch de gd rp so
# OBJ	rp	OPT	tc ny ma
# OBJ	rp	MULT	ac de tc ch ny
# OBJ	rp	SORT	2
# OBJ	rp	UNIQ	rp
# OBJ	rp	KEYS	rp
# OBJ	rp	REC	ac tc

#	clns object
#
OBJ	dp	ATSQ	dp da de bi dm do df ac tc gd rm ny ma mb ch so
OBJ	dp	MAND	dp da ac tc ch so
OBJ	dp	OPT	bi de dm do df gd ny ma rm mb
OBJ	dp	MULT	de bi dm do df ac tc ch ny rm mb
OBJ	dp	SORT	7
OBJ	dp	UNIQ	dp
OBJ	dp	KEYS	dp da
OBJ	dp	REC	ac tc
OBJ	dp	OBS	ma

#       inet-rtr
#
OBJ     ir      ATSQ    ir la if pe ac tc rm ny mb ch so
OBJ     ir      MAND    ir la if tc ac ch so
OBJ     ir      OPT     pe ny mb rm
OBJ     ir      MULT    if pe tc ac rm ny ch mb
OBJ     ir      SORT    9
OBJ     ir      UNIQ    ir
OBJ     ir      KEYS    ir if
OBJ     ir      REC     tc ac

#       maintainer
#
OBJ     mt      ATSQ    mt de ac tc dt mn at rm ny mb ch so
OBJ     mt      MAND    mt de ac dt at ch so
OBJ     mt      OPT     tc mn rm ny mb
OBJ     mt      MULT    de ac tc dt mn at rm ny mb ch
OBJ     mt      SORT    10
OBJ     mt      UNIQ    mt
OBJ     mt      KEYS    mt
OBJ     mt      REC     ac tc

#       route - ONLY PRDB SUPPORTS THESE CURRENTLY
#
# OBJ     rt      ATSQ    rt de or ho wd cl lr rm ny mb ch so
# OBJ     rt      MAND    rt de or ch so
# OBJ     rt      OPT     ho wd cl rm ny mb la
# OBJ     rt      MULT    de ho cl rm ny ch mb
# OBJ     rt      SORT    11
# OBJ     rt      UNIQ    rt or
# OBJ     rt      KEYS    rt

# MAILCMD is the command into which a composed e-mail is given as standard
# input, to be send as mail. The message piped into this command has ALL
# the necessary mail header to process the mail:
# From:
# To:
# Subject:
# The mail command should take the recipients from the actual message.
# Using sendmail it will be executed as: /usr/lib/sendmail -t < "messagefile"
# (default: /usr/lib/sendmail -t)
#
# NOTE:
# -fripe-dbm makes ripe-dbm the trusted user that will appear on the
# envelope. Bounces will go to this address. If you do not specify
# this, sendmail will send bounces straight back to the automatic
# mailbox, where it will bounce again, and again, ....
# User has to be a trusted user, T<name> in sendmail.cf.

MAILCMD /usr/lib/sendmail -fripe-dbm -t

# The MAILTXT is the text that comes right after the headers in an email ack
# send by "dbupdate" when processing an email update (-M flag).
# In this text you can use 4 variables that will be expanded to the real
# values in the ack:
#
# $FROM		= "Reply-To:" or "From:" address in mail being processed
# $SUBJECT	= "Subject:" field                   ,,          ,,
# $MDATE	= "Date:" field	                     ,,          ,,
# $MSGID	= "Msg-Id:" field                    ,,          ,,

MAILTXT	
MAILTXT	Your e-mail:
MAILTXT
MAILTXT >   From:    $FROM
MAILTXT >   Subject: $SUBJECT
MAILTXT	>   Date:    $MDATE
MAILTXT	>   Msg-Id:  $MSGID
MAILTXT
MAILTXT has been processed by the automatic update procedure at the RIPE NCC.
MAILTXT Diagnostic output follows:
MAILTXT
MAILTXT ------------------------------------------------------------------------

# MHEADER The complete mailheader for the ack mail, you can include any
# mail header field, EXCEPT for the "To:" field which is added inside the
# ack sending program. Again you can use the 4 variables as specified in
# MAILTXT

MHEADER	From: RIPE Database Management <ripe-dbm@ripe.net>
MHEADER	Subject: Re: $SUBJECT
MHEADER Reply-To: ripe-dbm@ripe.net
MHEADER Precedence: bulk

# ACKERR is the message that will be displayed when errors or warnings were
# found in an update.

ACKERR
ACKERR Objects that just generated a WARNING have been updated as shown.
ACKERR
ACKERR Objects that generated an *ERROR* have NOT been updated as requested.
ACKERR Please re-submit corrected objects.

# ACKOK is message displayed when no error/warnings were found in an update

ACKOK	
ACKOK	No error/warnings were found in your database update.  Congratulations.

# Signature on the acknowledgement

ACKSIG ------------------------------------------------------------------------
ACKSIG
ACKSIG Please use 
ACKSIG
ACKSIG     <auto-dbm@ripe.net>     instead of  <ripe-dbm@ripe.net>   and
ACKSIG     <auto-assign@ripe.net>  instead of  <assign@ripe.net> 
ACKSIG
ACKSIG for fast turnaround times on all but guarded objects.
ACKSIG
ACKSIG If you have any question about an error or warning message, please
ACKSIG contact <ripe-dbm@ripe.net>.
ACKSIG
ACKSIG Sincerely Yours, 
ACKSIG
ACKSIG Latest and Greatest RIPE Database Maintenance Department (Automatic Section)

# NOTITXT Notification text used in notification messages.
# Same variables as in MAILTXT can be used here.

NOTITXT Dear Colleague,
NOTITXT
NOTITXT This is to notify you that some objects in which you are mentioned as
NOTITXT a notifier, guardian or maintainer of one of the guarded attributes
NOTITXT in this object have been modified in the NEW RIPE database.
NOTITXT The objects below are the NEW entries for these
NOTITXT objects in the database. In case of DELETIONS, the deleted object is
NOTITXT displayed. NOOPs will not be reported.
NOTITXT
NOTITXT The update causing these changes had the following mail headers:
NOTITXT
NOTITXT - From:    $FROM
NOTITXT - Subject: $SUBJECT
NOTITXT - Date:    $MDATE
NOTITXT - Msg-Id:  $MSGID
NOTITXT
NOTITXT RIPE Database Notification Department

# NHEADER The Header used for notification messages

NHEADER From: RIPE Database Notifications <ripe-dbm@ripe.net>
NHEADER Subject: Notification of RIPE Database changes
NHEADER Reply-To: ripe-dbm@ripe.net

# FWHEADER The header for forwarding updates that failed because of
# maintainer autorisation failures.

FWHEADER From: RIPE Database Maintainer Forwarding <ripe-dbm@ripe.net>
FWHEADER Subject: Requested RIPE database object changes
FWHEADER Reply-To: ripe-dbm@ripe.net

# FWTEXT The text send out to maintainers to inform them that someone
# tried to change objects for which they are maintainers, but failed
# the authorisation

FWTEXT
FWTEXT  Dear Maintainer,
FWTEXT
FWTEXT  This is to notify you that some objects in which you are mentioned as
FWTEXT  a maintainer were requested to be changed, but *failed* the proper
FWTEXT  authorisation for any of the mentioned maintainers.
FWTEXT  Please contact the sender of these changes about changes that need
FWTEXT  need to be made to the following objects.
FWTEXT
FWTEXT  The mail message causing these failures had the following mail headers:
FWTEXT
FWTEXT  - From:    $FROM
FWTEXT  - Subject: $SUBJECT
FWTEXT  - Date:    $MDATE
FWTEXT  - Msg-Id:  $MSGID
FWTEXT
FWTEXT  RIPE Database Maintainer Forwarding Department

# Maintainer objects are handles special and cannot be created auto
# automatically. They are forwarded to $HUMAILBOX or whatever you
# want to specify. The ERROR sent back to the sender, will contain
# $HUMAILBOX as the mailbox it was sent to. This one can take variable
# substitution like MAILTXT.

MTFWHEADER To: $HUMAILBOX
MTFWHEADER From: RIPE Database Maintainer Creation <$HUMAILBOX>
MTFWHEADER Subject: Maintainer Creation request
MTFWHEADER Reply-To: $HUMAILBOX

# And this is the text of the message that will be sent in the above case.

MTFWTEXT A maintainer object is requested by:
MTFWTEXT
MTFWTEXT - From:    $FROM
MTFWTEXT - Subject: $SUBJECT
MTFWTEXT - Date:    $MDATE
MTFWTEXT - Msg-Id:  $MSGID
MTFWTEXT
MTFWTEXT Please process the object below.
MTFWTEXT

# COPYRIGHT message that goes on top of every newly generated, or cleaned
# database, will be output with "#" before each line.

RIGHTS Copyright (c)1992/1993/1994 by Daniel Karrenberg and the RARE Association
RIGHTS
RIGHTS Restricted rights.
RIGHTS
RIGHTS Except for agreed Internet operational purposes, no part of this
RIGHTS publication may be reproduced, stored in a retrieval system, or
RIGHTS transmitted, in any form or by any means, electronic, mechanical,
RIGHTS recording, or otherwise, without prior permission of the RIPE NCC
RIGHTS on behalf of the copyright holders. Any use of this material to
RIGHTS target advertising or similar activities are explicitly forbidden
RIGHTS and will be prosecuted.  The RIPE NCC requests to be notified of
RIGHTS any such activities or suspicions thereof.

# the list of valid country names RIPE database specific, used
# for syntax checking. May move into different config at later stage.

COUNTRY AE ae
COUNTRY AL al
COUNTRY AM am
COUNTRY AT at
COUNTRY AZ az
COUNTRY BE be
COUNTRY BF bf
COUNTRY BG bg
COUNTRY BH bh
COUNTRY BY by
COUNTRY CH ch
COUNTRY CM cm
COUNTRY CS cs
COUNTRY CZ cz
COUNTRY CY cy
COUNTRY DE de
COUNTRY DK dk
COUNTRY DZ dz
COUNTRY EE ee
COUNTRY EG eg
COUNTRY ES es
COUNTRY FI fi
COUNTRY FR fr
COUNTRY GB gb
COUNTRY GR gr
COUNTRY HR hr
COUNTRY HU hu
COUNTRY IE ie
COUNTRY IL il
COUNTRY IN in
COUNTRY IR ir
COUNTRY IS is
COUNTRY IT it
COUNTRY KE ke
COUNTRY KG kg
COUNTRY KW kw
COUNTRY KZ kz
COUNTRY LA la
COUNTRY LB lb
COUNTRY LI li
COUNTRY LU lu
COUNTRY LV lv
COUNTRY LT lt
COUNTRY MA ma
COUNTRY MC mc
COUNTRY MK mk
COUNTRY MT mt
COUNTRY NC nc
COUNTRY NE ne
COUNTRY NL nl
COUNTRY NO no
COUNTRY OM om
COUNTRY PF pf
COUNTRY PL pl
COUNTRY PT pt
COUNTRY RO ro
COUNTRY RU ru
COUNTRY SA sa
COUNTRY SE se
COUNTRY SG sg
COUNTRY SI si
COUNTRY SK sk
COUNTRY SN sn
COUNTRY SU su
COUNTRY TN tn
COUNTRY TR tr
COUNTRY UA ua
COUNTRY US us
COUNTRY UZ uz
COUNTRY YU yu
COUNTRY ZA za

# And some funny translations for the yobbos

COUNTRY GB UK
COUNTRY GB uk

# legal connect attribute values in alphabetic order
# also RIPE database specific used for syntax checking, may move to
# different config file later ....
#
# In fact they are obsoleted.
#
CONNECT ACONET
CONNECT ALT
CONNECT CIX
CONNECT CNR
CONNECT	DATANET
CONNECT EASI
CONNECT	EBONE
CONNECT	EMPB
CONNECT EU
CONNECT EU-FI
CONNECT FICIX
CONNECT FUNET
CONNECT GARR
CONNECT HEPNET
CONNECT ICS
CONNECT INFN
CONNECT IRIS
CONNECT IUNET
CONNECT JANET
CONNECT LANLINK
CONNECT LOCAL
CONNECT NETTUNO
CONNECT NIKHEF
CONNECT NLNET
CONNECT NORDU
CONNECT NSF
CONNECT PIPEX
CONNECT POWERWAN
CONNECT RCCN
CONNECT REDIRIS
CONNECT RENATER
CONNECT RIPE
CONNECT SARA
CONNECT SURF
CONNECT SWIP
CONNECT SWITCH
CONNECT TIP
CONNECT WCW
CONNECT WIN
CONNECT XLINK

ENDCONF		# do not remove!
