migration revision 16f5a913cedbb0a65471a28354ef85f196099bb5
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinCopyright (C) 2004, 2007 Internet Systems Consortium, Inc. ("ISC")
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic UpdaterCopyright (C) 2000, 2001, 2003 Internet Software Consortium.
75c0816e8295e180f4bc7f10db3d0d880383bc1cMark AndrewsSee COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
4a14ce5ba00ab7bc55c99ffdcf59c7a4ab902721Automatic Updater BIND 8 to BIND 9 Migration Notes
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 is designed to be mostly upwards compatible with BIND 8, but
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthere is still a number of caveats you should be aware of when
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinupgrading an existing BIND 8 installation to use BIND 9.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein1. Configuration File Compatibility
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein1.1. Unimplemented Options and Changed Defaults
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 supports most, but not all of the named.conf options of BIND 8.
4a14ce5ba00ab7bc55c99ffdcf59c7a4ab902721Automatic UpdaterFor a complete list of implemented options, see doc/misc/options.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinIf your named.conf file uses an unimplemented option, named will log a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinwarning message. A message is also logged about each option whose
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeindefault has changed unless the option is set explicitly in named.conf.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe default of the "transfer-format" option has changed from
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein"one-answer" to "many-answers". If you have slave servers that do not
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinunderstand the many-answers zone transfer format (e.g., BIND 4.9.5 or
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinolder) you need to explicitly specify "transfer-format one-answer;" in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeineither the options block or a server statement.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein1.2. Handling of Configuration File Errors
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinIn BIND 9, named refuses to start if it detects an error in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnamed.conf. Earlier versions would start despite errors, causing the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinserver to run with a partial configuration. Errors detected during
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinsubsequent reloads do not cause the server to exit.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinErrors in master files do not cause the server to exit, but they
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeindo cause the zone not to load.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe set of logging categories in BIND 9 is different from that
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinin BIND 8. If you have customised your logging on a per-category
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinbasis, you need to modify your logging statement to use the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnew categories.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinAnother difference is that the "logging" statement only takes effect
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinafter the entire named.conf file has been read. This means that when
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updaterthe server starts up, any messages about errors in the configuration
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updaterfile are always logged to the default destination (syslog) when the
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updaterserver first starts up, regardless of the contents of the "logging"
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updaterstatement. In BIND 8, the new logging configuration took effect
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinimmediately after the "logging" statement was read.
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updater1.4. Notify messages and Refresh queries
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic UpdaterThe source address and port for these is now controlled by
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updater"notify-source" and "transfer-source", respectively, rather that
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updaterquery-source as in BIND 8.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein1.5. Multiple Classes.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinMultiple classes have to be put into explicit views for each class.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2. Zone File Compatibility
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.1. Strict RFC1035 Interpretation of TTLs in Zone Files
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 strictly complies with the RFC1035 and RFC2308 rules regarding
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinomitted TTLs in zone files. Omitted TTLs are replaced by the value
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinspecified with the $TTL directive, or by the previous explicit TTL if
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthere is no $TTL directive.
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic UpdaterIf there is no $TTL directive and the first RR in the file does not
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinhave an explicit TTL field, the zone file is illegal according to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinRFC1035 since the TTL of the first RR is undefined. Unfortunately,
c48c7872a0e020a63a96faed166c6ae960e4c1e9Mark AndrewsBIND 4 and many versions of BIND 8 accept such files without warning
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinand use the value of the SOA MINTTL field as a default for missing TTL
71c66a876ecca77923638d3f94cc0783152b2f03Mark AndrewsBIND 9.0 and 9.1 completely refused to load such files. BIND 9.2
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrewsemulates the nonstandard BIND 4/8 SOA MINTTL behaviour and loads the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinfiles anyway (provided the SOA is the first record in the file), but
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinwill issue the warning message "no TTL specified; using SOA MINTTL
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinTo avoid problems, we recommend that you use a $TTL directive in each
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updater2.2. Periods in SOA Serial Numbers Deprecated
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic UpdaterSome versions of BIND allow SOA serial numbers with an embedded
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updaterperiod, like "3.002", and convert them into integers in a rather
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrewsunintuitive way. This feature is not supported by BIND 9; serial
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updaternumbers must be integers.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.3. Handling of Unbalanced Quotes
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinTXT records with unbalanced quotes, like 'host TXT "foo', were not
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updatertreated as errors in some versions of BIND. If your zone files
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeincontain such records, you will get potentially confusing error
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updatermessages like "unexpected end of file" because BIND 9 will interpret
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrewseverything up to the next quote character as a literal string.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.4. Handling of Line Breaks
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinSome versions of BIND accept RRs containing line breaks that are not
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updaterproperly quoted with parentheses, like the following SOA:
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrews ( 1 3600 1800 1814400 3600 )
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThis is not legal master file syntax and will be treated as an error
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinby BIND 9. The fix is to move the opening parenthesis to the first
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.5. Unimplemented BIND 8 Extensions
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updater$GENERATE: The "$$" construct for getting a literal $ into a domain
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinname is deprecated. Use \$ instead.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.6. TXT records are no longer automatically split.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinSome versions of BIND accepted strings in TXT RDATA consisting of more
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthan 255 characters and silently split them to be able to encode the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinstrings in a protocol conformant way. You may now see errors like this
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein dns_rdata_fromtext: local.db:119: ran out of space
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinif you have TXT RRs with too longs strings. Make sure to split the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinstring in the zone data file at or before a single one reaches 255
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein3. Interoperability Impact of New Protocol Features
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size. It
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinalso sets DO EDNS flag bit in queries to indicate that it wishes to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinreceive DNSSEC responses.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinMost older servers that do not support EDNS0, including prior versions
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinof BIND, will send a FORMERR or NOTIMP response to these queries.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinWhen this happens, BIND 9 will automatically retry the query without
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinUnfortunately, there exists at least one non-BIND name server
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinimplementation that silently ignores these queries instead of sending
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinan error response. Resolving names in zones where all or most
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinauthoritative servers use this server will be very slow or fail
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeincompletely. We have contacted the manufacturer of the name server in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeincase, and they are working on a solution.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinWhen BIND 9 communicates with a server that does support EDNS0, such as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinanother BIND 9 server, responses of up to 4096 bytes may be
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeintransmitted as a single UDP datagram which is subject to fragmentation
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinat the IP level. If a firewall incorrectly drops IP fragments, it can
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeincause resolution to slow down dramatically or fail.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein3.2. Zone Transfers
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinOutgoing zone transfers now use the "many-answers" format by default.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThis format is not understood by certain old versions of BIND 4.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinYou can work around this problem using the option "transfer-format
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinone-answer;", but since these old versions all have known security
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinproblems, the correct fix is to upgrade the slave servers.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinZone transfers to Windows 2000 DNS servers sometimes fail due to a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinbug in the Windows 2000 DNS server where DNS messages larger than
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein16K are not handled properly. Obtain the latest service pack for
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinWindows 2000 from Microsoft to address this issue. In the meantime,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthe problem can be worked around by setting "transfer-format one-answer;".
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinhttp://support.microsoft.com/default.aspx?scid=kb;en-us;297936
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein4. Unrestricted Character Set
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein BIND 9.2 only
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 does not restrict the character set of domain names - it is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinfully 8-bit clean in accordance with RFC2181 section 11.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinIt is strongly recommended that hostnames published in the DNS follow
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthe RFC952 rules, but BIND 9 will not enforce this restriction.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinHistorically, some applications have suffered from security flaws
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrewswhere data originating from the network, such as names returned by
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeingethostbyaddr(), are used with insufficient checking and may cause a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinbreach of security when containing unexpected characters; see
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<http://www.cert.org/advisories/CA-96.04.corrupt_info_from_servers.html>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinfor details. Some earlier versions of BIND attempt to protect these
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinflawed applications from attack by discarding data containing
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeincharacters deemed inappropriate in host names or mail addresses, under
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinthe control of the "check-names" option in named.conf and/or "options
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinno-check-names" in resolv.conf. BIND 9 provides no such protection;
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinif applications with these flaws are still being used, they should
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein BIND 9.3 onwards implements check-names.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein5. Server Administration Tools
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein5.1 Ndc Replaced by Rndc
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe "ndc" program has been replaced by "rndc", which is capable of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinremote operation. Unlike ndc, rndc requires a configuration file.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe easiest way to generate a configuration file is to run
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein"rndc-confgen -a"; see the man pages for rndc(8), rndc-confgen(8),
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinand rndc.conf(5) for details.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein5.2. Nsupdate Differences
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe BIND 8 implementation of nsupdate had an undocumented feature
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinwhere an update request would be broken down into multiple requests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinbased upon the discovered zones that contained the records. This
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinbehaviour has not been implemented in BIND 9. Each update request
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinmust pertain to a single zone, but it is still possible to do multiple
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinupdates in a single invocation of nsupdate by terminating each update
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinwith an empty line or a "send" command.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein6. No Information Leakage between Zones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 9 stores the authoritative data for each zone in a separate data
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinstructure, as recommended in RFC1035 and as required by DNSSEC and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinIXFR. When a BIND 9 server is authoritative for both a child zone and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinits parent, it will have two distinct sets of NS records at the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeindelegation point: the authoritative NS records at the child's apex,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinand a set of glue NS records in the parent.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinBIND 8 was unable to properly distinguish between these two sets of NS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinrecords and would "leak" the child's NS records into the parent,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeineffectively causing the parent zone to be silently modified: responses
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinand zone transfers from the parent contained the child's NS records
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinrather than the glue configured into the parent (if any). In the case
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinof children of type "stub", this behaviour was documented as a feature,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinallowing the glue NS records to be omitted from the parent
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinconfiguration.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinSites that were relying on this BIND 8 behaviour need to add any
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinomitted glue NS records, and any necessary glue A records, to the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinAlthough stub zones can no longer be used as a mechanism for injecting
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinNS records into their parent zones, they are still useful as a way of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeindirecting queries for a given domain to a particular set of name
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein7. Umask not Modified
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark AndrewsThe BIND 8 named unconditionally sets the umask to 022. BIND 9 does
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrewsnot; the umask inherited from the parent process remains in effect.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThis may cause files created by named, such as journal files, to be
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrewscreated with different file permissions than they did in BIND 8. If
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnecessary, the umask should be set explicitly in the script used to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinstart the named process.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$Id: migration,v 1.48 2007/08/23 23:46:43 tbox Exp $