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
93 .IR socket ; if running a new server, instruct it to listen for admin
97 .BI "\-P, \-\-pidfile=" pidfile
108 options are given, a default of
109 .IB dir /tripectl.pid
110 is used if you don't give a
115 Start a new server: don't connect to an existing one. Starting a
117 server in this manner is a good way to ensure that no log messages are
123 options are particularly useful in conjunction with
126 .BI "\-p, \-\-spawn\-path=" path
129 runs the program named by
131 rather than the default
135 is actually an unqualified filename, the program to run is found using
138 environment variable in the usual way.
140 .BI "\-S, \-\-spawn\-args=" arg , arg ,\fR...
143 passes the comma-separated
147 server on its command line. Arguments added using this option are added
149 any passed automatically by
155 Send warnings and trace messages to the
157 service. Messages are logged using the
159 facility. Warnings are logged with severity
161 trace messages are logged with severity
164 .BI "\-f, \-\-logfile=" file
165 Write warnings and trace messages to
171 will close its log file and reopen a new one with the same name. This
172 is useful when you rotate logs.
174 .B "\-w, \-\-warnings"
175 Write warnings to standard error even when running noninteractively.
176 .SS "Interactive use"
179 will connect to a running server and await commands from its standard
180 input. The commands are submitted to the server unchanged, and the
181 results written to standard output. It will quit when it receives a
182 fatal signal or an end-of-file indication from the server.
183 .SS "Use from scripts"
184 If arguments are given to
186 they are concatenated with spaces between and submitted to the server
187 after connection. Any
189 responses returned by the server are written to standard output (without
194 response causes the error message to be written to standard error, and
195 the client to exit with a nonzero return code. An
197 response causes the client to exit with a zero return code. Unless the
199 command-line option was given, any
201 responses are discarded; if
206 responses are written to standard error. In all cases,
208 responses are ignored.
209 .SS "Starting the tripe server"
210 If any of the options
219 server, rather than connecting to an existing one. This is most useful
220 if you want to collect logging information from the server, and want to
221 avoid losing any. For example, the command
223 tripectl -Ds -f tripe.log
225 starts up a new server in the default directory, and captures all of its
226 logging output (i.e.,
230 messages) in the file
232 It stores its process-id in
235 It's possible to communicate interactively with a newly-started server,
236 or to give it a command and quit, but this is seldom useful.
238 .BR tripe\-admin (5),
241 .IR "The Trivial IP Encryption Protocol" ,
242 .IR "The Wrestlers Protocol" .
244 Mark Wooding, <mdw@nsict.org>