Commit dd166411 authored by Daniel Salzman's avatar Daniel Salzman

Update README

parent 4922bdfe
...@@ -157,27 +157,27 @@ Running ...@@ -157,27 +157,27 @@ Running
First, each server needs configuration file. First, each server needs configuration file.
Please see samples/knot.sample.conf for reference. Please see samples/knot.sample.conf for reference.
Minimal configuration can be found in samples/knot.min.conf More examples can be found in samples/knot.full.conf
Configuration file has to specify: Configuration file has to specify:
* storage for PID files, journal files etc. * storage for PID files, journal files etc.
* network interfaces * network interfaces
* served zones * served zones
$ cp samples/knot.min.conf myserver.conf $ cp samples/knot.sample.conf myserver.conf
$ vim myserver.conf # or your favourite text editor $ vim myserver.conf # or your favourite text editor
$ knotc -h # see what it can do $ knotd -h # see what it can do
Prepare working directory. Second, prepare working directory.
$ mkdir -p /tmp/knot-minimal/samples; cp samples/example.com.zone /tmp/knot-minimal/samples/ $ mkdir -p /tmp/knot-minimal/samples; cp samples/example.com.zone /tmp/knot-minimal/samples/
Third, let's start the server. This can be done by running the 'knotd' command. Third, let's start the server. This can be done by running the 'knotd' command.
Alternatively, your distribution should have an init script available, if you've installed Alternatively, your distribution should have an init script available, if you've
Knot using a binary package. installed Knot using a binary package.
Lets start our server in foreground to see if it runs: Lets start our server in foreground to see if it runs:
$ knotd -c myserver.conf # start server $ knotd -c myserver.conf
For more information, refer to the user manual. For more information, refer to the user manual.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment