root/docs/operation/noitd.xml

Revision 23dea7e00df87480acb58bb3398283c2bb227949, 1.3 kB (checked in by Theo Schlossnagle <jesus@omniti.com>, 3 years ago)

pull docs into master

  • Property mode set to 100644
Line 
1 <?xml version='1.0' encoding='UTF-8' ?>
2 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
4 [
5   <!ENTITY % magic.fixup SYSTEM "http://labs.omniti.com/docbook/ent">
6   %magic.fixup;
7 ]>
8 <chapter id="operation.noitd">
9   <title>Operating the noitd daemon</title>
10
11 <para>
12 Once <command>noitd</command> is configured and running, there
13 are several methods of interacting with the service.  The operator
14 can interactively manage the instance via the integrated command line
15 console (accessible via telnet on the port of your choice, as configured
16 in noitd.conf via listener elements; by default port 32322) and
17 programmatic access is available over the <command>noitd</command>
18 wire protocol on port 43191.
19 </para>
20
21 <para>
22 The wire protocol is a binary protocol that is leverage for
23 inter-system communication.  While not entirely compliant with
24 the HTTP specification, the protocol will give well formed HTTP
25 responses to sessions that commence with the terms: "DELETE"
26 "GET " "HEAD" "POST" "PUT ".
27 </para>
28
29 <section id="noitd.interactive.console">
30 <title><command>noitd</command> Interactive Console</title>
31 &operation.cli.all;
32 </section>
33
34 <section id="noitd.wire.protocol">
35 <title><command>noitd</command> Wire Protocol</title>
36 &operation.wire.all;
37 </section>
38
39 </chapter>
Note: See TracBrowser for help on using the browser.