19 .TH tripectl 1 "19 February 2001" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
21 tripectl \- simple client for TrIPE
50 .IB arg , arg ,\fR...]
54 is a simple client which can be used, either interactively or from a
55 script, to send commands to and read status information from a running
57 server. It can also be used to start
59 passing appropriate arguments and capturing logging information.
60 .SS "Command-line options"
63 Writes a brief description of the command-line options available to
64 standard output and exits with status 0.
67 Writes tripe's version number to standard output and exits with status
71 Writes a brief usage summary to standard output and exits with status 0.
76 disassociate from the terminal and become a background process after
77 connecting to the server.
79 .BI "\-d, \-\-directory=" dir
82 the current directory, before doing anything else. Note that all the
83 other filenames (e.g., the log output file) are relative to this
84 directory. The default directory, if this option is not specified, is
85 taken from the environment variable
87 if that's not defined either, a default default of
91 .BI "\-a, \-\-admin=" socket
92 If connecting to a running server, connect to the socket named
94 if running a new server, instruct it to listen for admin
98 .BI "\-P, \-\-pidfile=" pidfile
109 options are given, a default of
110 .IB dir /tripectl.pid
111 is used if you don't give a
116 Start a new server: don't connect to an existing one. Starting a
118 server in this manner is a good way to ensure that no log messages are
124 options are particularly useful in conjunction with
127 .BI "\-p, \-\-spawn\-path=" path
130 runs the program named by
132 rather than the default
136 is actually an unqualified filename, the program to run is found using
139 environment variable in the usual way.
141 .BI "\-S, \-\-spawn\-args=" arg , arg ,\fR...
144 passes the comma-separated
148 server on its command line. Arguments added using this option are added
150 any passed automatically by
156 Send warnings and trace messages to the
158 service. Messages are logged using the
160 facility. Warnings are logged with severity
162 trace messages are logged with severity
165 .BI "\-f, \-\-logfile=" file
166 Write warnings and trace messages to
172 will close its log file and reopen a new one with the same name. This
173 is useful when you rotate logs.
175 .B "\-w, \-\-warnings"
176 Write warnings to standard error even when running noninteractively.
177 .SS "Interactive use"
180 will connect to a running server and await commands from its standard
181 input. The commands are submitted to the server unchanged, and the
182 results written to standard output. It will quit when it receives a
183 fatal signal or an end-of-file indication from the server.
184 .SS "Use from scripts"
185 If arguments are given to
187 they are concatenated with spaces between and submitted to the server
188 after connection. Any
190 responses returned by the server are written to standard output (without
195 response causes the error message to be written to standard error, and
196 the client to exit with a nonzero return code. An
198 response causes the client to exit with a zero return code. Unless the
200 command-line option was given, any
202 responses are discarded; if
207 responses are written to standard error. In all cases,
209 responses are ignored.
210 .SS "Starting the tripe server"
211 If any of the options
220 server, rather than connecting to an existing one. This is most useful
221 if you want to collect logging information from the server, and want to
222 avoid losing any. For example, the command
224 tripectl -Ds -f tripe.log
226 starts up a new server in the default directory, and captures all of its
227 logging output (i.e.,
231 messages) in the file
233 It stores its process-id in
236 It's possible to communicate interactively with a newly-started server,
237 or to give it a command and quit, but this is seldom useful.
239 .BR tripe\-admin (5),
242 .IR "The Trivial IP Encryption Protocol" ,
243 .IR "The Wrestlers Protocol" .
245 Mark Wooding, <mdw@nsict.org>