PageRenderTime 40ms CodeModel.GetById 14ms RepoModel.GetById 1ms app.codeStats 0ms

/conman-0.2.7/man/conman.conf.5.in

#
Autoconf | 330 lines | 318 code | 12 blank | 0 comment | 31 complexity | 0f56eb1b8c6acec9fb9dfe8c6983e6c9 MD5 | raw file
Possible License(s): GPL-3.0
  1. .\" $Id: conman.conf.5.in 1059 2011-04-21 00:20:12Z chris.m.dunlap $
  2. .TH CONMAN.CONF 5 "@DATE@" "@PROJECT@-@VERSION@" "ConMan: The Console Manager"
  3. .SH NAME
  4. conman.conf \- ConMan daemon configuration file
  5. .SH DESCRIPTION
  6. The \fBconman.conf\fR configuration file is used to specify the consoles
  7. being managed by \fBconmand\fR.
  8. .PP
  9. Comments are introduced by a hash sign (#), and continue until the end
  10. of the line. Blank lines and white-space are ignored. Directives are
  11. terminated by a newline, but may span multiple lines by escaping it (i.e.,
  12. immediately preceding the newline with a backslash). Strings may be
  13. either single-quoted or double-quoted, but they may not contain newlines.
  14. Keywords are case-insensitive.
  15. .SH SERVER DIRECTIVES
  16. These directives begin with the \fBSERVER\fR keyword followed by one of the
  17. following key/value pairs:
  18. .TP
  19. \fBcoredump\fR \fB=\fR (\fBon\fR|\fBoff\fR)
  20. Specifies whether the daemon should generate a core dump file. This file
  21. will be created in the current working directory (or '/' when running in the
  22. background) unless you also set \fBcoredumpdir\fR. The default is \fboff\fR.
  23. .TP
  24. \fBcoredumpdir\fR \fB=\fR "\fIdirectory\fR"
  25. Specifies the directory where the daemon tries to write core dump files.
  26. The default is empty, meaning the current working directory (or '/' when
  27. running in the background) will be used.
  28. .TP
  29. \fBexecpath\fR \fB=\fR "\fIdir1:dir2:dir3...\fR"
  30. Specifies a colon-separated list of directories in which to search for external
  31. process-based console executables that are not defined by an absolute or
  32. relative pathname. The default is empty.
  33. .TP
  34. \fBkeepalive\fR \fB=\fR (\fBon\fR|\fBoff\fR)
  35. Specifies whether the daemon will use TCP keep-alives for detecting dead
  36. connections. The default is \fBon\fR.
  37. .TP
  38. \fBlogdir\fR \fB=\fR "\fIdirectory\fR"
  39. Specifies a directory prefix for log files that are not defined via an
  40. absolute pathname. This affects the \fBserver logfile\fR, \fBglobal log\fR,
  41. and \fBconsole log\fR directives.
  42. .TP
  43. \fBlogfile\fR \fB=\fR "\fIfile\fR[,\fIpriority\fR]"
  44. Specifies the file to which log messages are appended if the daemon is
  45. not running in the foreground. This string undergoes conversion specifier
  46. expansion (cf., \fBCONVERSION SPECIFICATIONS\fR) each time the file is opened.
  47. If an absolute pathname is not given, the file's location is relative
  48. to either \fBlogdir\fR (if defined) or the current working directory.
  49. Intermediate directories will be created as needed. The filename may
  50. optionally be followed by a comma and a minimum priority at which messages
  51. will be logged. Refer to \fBsyslog.conf(5)\fR for a list of priorities.
  52. The default priority is \fBinfo\fR. If this keyword is used in conjunction
  53. with the \fBsyslog\fR keyword, messages will be sent to both locations.
  54. .TP
  55. \fBloopback\fR \fB=\fR (\fBon\fR|\fBoff\fR)
  56. Specifies whether the daemon will bind its socket to the loopback address,
  57. thereby only accepting local client connections directed to that address
  58. (127.0.0.1). The default is \fBoff\fR.
  59. .TP
  60. \fBpidfile\fR \fB=\fR "\fIfile\fR"
  61. Specifies the file to which the daemon's PID is written. Intermediate
  62. directories will be created as needed. The use of a pidfile is recommended
  63. if you want to use the daemon's '\fB-k\fR', '\fB-q\fR', or '\fB-r\fR' options.
  64. .TP
  65. \fBport\fR \fB=\fR \fIinteger\fR
  66. Specifies the port on which the daemon will listen for client connections.
  67. .TP
  68. \fBresetcmd\fR \fB=\fR "\fIstring\fR"
  69. Specifies a command string to be invoked by a subshell upon receipt
  70. of the client's "reset" escape. Multiple commands within a string
  71. may be separated with semicolons. This string undergoes conversion
  72. specifier expansion (cf., \fBCONVERSION SPECIFICATIONS\fR) and will be
  73. invoked multiple times if the client is connected to multiple consoles.
  74. .TP
  75. \fBsyslog\fR \fB=\fR "\fIfacility\fR"
  76. Specifies that log messages are to be sent to the system logger
  77. (\fBsyslogd\fR) at the given facility. Refer to \fBsyslog.conf(5)\fR for a
  78. list of facilities. If this keyword is used in conjunction with the
  79. \fBlogfile\fR keyword, messages will be sent to both locations.
  80. .TP
  81. \fBtcpwrappers\fR \fB=\fR (\fBon\fR|\fBoff\fR)
  82. Specifies whether the daemon will use TCP-Wrappers when accepting client
  83. connections. Support for this feature must be enabled at compile-time (via
  84. configure's "--with-tcp-wrappers" option). Refer to \fBhosts_access(5)\fR
  85. and \fBhosts_options(5)\fR for more details. The default is \fBoff\fR.
  86. .TP
  87. \fBtimestamp\fR \fB=\fR \fIinteger\fB (\fBm\fR|\fBh\fR|\fBd\fR)
  88. Specifies the interval between timestamps written to the individual
  89. console log files. The interval is an integer that may be followed by a
  90. single-character modifier; '\fBm\fR' for minutes (the default), '\fBh\fR'
  91. for hours, or '\fBd\fR' for days. The default is 0 (i.e., no timestamps).
  92. .SH GLOBAL DIRECTIVES
  93. These directives begin with the \fBGLOBAL\fR keyword followed by one of the
  94. following key/value pairs:
  95. .TP
  96. \fBlog\fR \fB=\fR "\fIfile\fR"
  97. Specifies the default log file to use for each \fBconsole\fR
  98. directive. This string undergoes conversion specifier expansion (cf.,
  99. \fBCONVERSION SPECIFICATIONS\fR) each time the file is opened; it must
  100. contain either '\fB%N\fR' or '\fB%D\fR'. If an absolute pathname is
  101. not given, the file's location is relative to either \fBlogdir\fR (if
  102. defined) or the current working directory. Intermediate directories
  103. will be created as needed.
  104. .TP
  105. \fBlogopts\fR \fB=\fR "(\fBlock\fR|\fBnolock\fR),(\fBsanitize\fR|\fBnosanitize\fR),(\fBtimestamp\fR|\fBnotimestamp\fR)"
  106. Specifies global options for the console log files. These options can be
  107. overridden on a per-console basis by specifying the \fBCONSOLE\fR \fBlogopts\fR
  108. keyword. Note that options affecting the output of the console's logfile also
  109. affect the output of the console's log-replay escape. The valid \fBlogopts\fR
  110. include the following:
  111. .br
  112. .sp
  113. \fBlock\fR or \fBnolock\fR - locked logs are protected with a write lock.
  114. .br
  115. .sp
  116. \fBsanitize\fR or \fBnosanitize\fR - sanitized logs convert non-printable
  117. characters into 7-bit printable characters.
  118. .br
  119. .sp
  120. \fBtimestamp\fR or \fBnotimestamp\fR - timestamped logs prepend each line
  121. of console output with a timestamp in "YYYY-MM-DD HH:MM:SS" format. This
  122. timestamp is generated when the first character following the line break is
  123. output.
  124. .br
  125. .sp
  126. The default is "\fBlock\fR,\fBnosanitize\fR,\fBnotimestamp\fR".
  127. .TP
  128. \fBseropts\fR \fB=\fR "\fIbps\fR[,\fIdatabits\fR[\fIparity\fR[\fIstopbits\fR]]]"
  129. Specifies global options for local serial devices. These options can be
  130. overridden on a per-console basis by specifying the \fBCONSOLE\fR
  131. \fBseropts\fR keyword.
  132. .br
  133. .sp
  134. \fIbps\fR is an integer specifying the baud rate in bits-per-second. If
  135. this exact value is not supported by the system, it will be rounded down to
  136. the next supported value.
  137. .br
  138. .sp
  139. \fIdatabits\fR is an integer from 5-8.
  140. .br
  141. .sp
  142. \fIparity\fR is a single case-insensitive character: '\fBn\fR'
  143. for none, '\fBo\fR' for odd, and '\fBe\fR' for even.
  144. .br
  145. .sp
  146. \fIstopbits\fR is an integer from 1-2.
  147. .br
  148. .sp
  149. The default is "9600,8n1" for 9600 bps, 8 data bits, no parity, and 1 stop bit.
  150. .TP
  151. \fBipmiopts\fR \fB=\fR "\fBU\fR:\fIstr\fR,\fBP\fR:\fIstr\fR,\fBK\fR:\fIstr\fR,\fBC\fR:\fIint\fR,\fBL\fR:\fIstr\fR,\fBW\fR:\fIflag\fR"
  152. Specifies global options for IPMI Serial-Over-LAN devices. These options can
  153. be overridden on a per-console basis by specifying the \fBCONSOLE\fR
  154. \fBIPMIOPTS\fR keyword. This directive is only available if configured using
  155. the "--with-freeipmi" option.
  156. .br
  157. .sp
  158. The \fBIPMIOPTS\fR string is parsed into comma-delimited substrings where each
  159. substring is of the form "\fIX\fR:\fIVALUE\fR". "\fIX\fR" is a
  160. single-character case-insensitive key specifying the option type, and
  161. "\fIVALUE\fR" is its corresponding value. The IPMI default will be used if
  162. either "\fIVALUE\fR" is omitted from the substring ("\fIX\fR:") or the
  163. substring is omitted altogether. Note that since the \fBIPMIOPTS\fR string is
  164. delimited by commas, substring values cannot contain commas.
  165. .br
  166. .sp
  167. The valid \fBIPMIOPTS\fR substrings include the following (in any order):
  168. .br
  169. .sp
  170. \fBU\fR:\fIusername\fR - a string of at most 16 bytes for the username with
  171. which to authenticate to the BMCs serving the remote consoles.
  172. .br
  173. .sp
  174. \fBP\fR:\fIpassword\fR - a string of at most 20 bytes for the password with
  175. which to authenticate to the BMCs serving the remote consoles.
  176. .br
  177. .sp
  178. \fBK\fR:\fIK_g\fR - a string of at most 20 bytes for the K_g key with which
  179. to authenticate to the BMCs serving the remote consoles.
  180. .br
  181. .sp
  182. \fBC\fR:\fIcipher_suite\fR - an integer for the IPMI cipher suite ID.
  183. Refer to \fBipmiconsole(8)\fR for a list of currently supported IDs.
  184. .br
  185. .sp
  186. \fBL\fR:\fIprivilege_level\fR - the string "user", "op", or "admin".
  187. .br
  188. .sp
  189. \fBW\fR:\fIworkaround_flag\fR - a string or integer for an IPMI workaround.
  190. Refer to \fBipmiconsole(8)\fR for a list of currently supported flags.
  191. This substring may be repeated to specify multiple workaround flags.
  192. .br
  193. .sp
  194. Both the \fIpassword\fR and \fIK_g\fR values can be specified in either ASCII
  195. or hexadecimal; in the latter case, the string should begin with "0x" and
  196. contain at most 40 hexadecimal digits. A \fIK_g\fR key entered in hexadecimal
  197. may contain embedded null characters, but any characters following the first
  198. null character in the \fIpassword\fR key will be ignored.
  199. .SH CONSOLE DIRECTIVES
  200. This directive defines an individual console being managed by the daemon.
  201. The \fBCONSOLE\fR keyword is followed by one or more of the following
  202. key/value pairs:
  203. .TP
  204. \fBname\fR \fB=\fR "\fIstring\fR"
  205. Specifies the name used by clients to refer to the console. This keyword is
  206. required.
  207. .TP
  208. \fBdev\fR \fB=\fR "\fIstring\fR"
  209. Specifies the type and location of the device. This keyword is required.
  210. .br
  211. .sp
  212. A local serial port connection is defined by the pathname of the character
  213. device file.
  214. .br
  215. .sp
  216. A remote terminal server connection using the telnet protocol is defined by
  217. the "\fIhost\fR:\fIport\fR" format (where \fIhost\fR is the remote hostname
  218. or IPv4 address, and \fIport\fR is the remote port number).
  219. .br
  220. .sp
  221. An external process-based connection is defined by the "\fIpath\fR
  222. \fIargs\fR" format (where \fIpath\fR is the pathname to an executable
  223. file/script, and any additional \fIargs\fR are space-delimited); the
  224. \fI@prefix@/lib/@PROJECT@/exec\fR directory contains scripts for various
  225. console types.
  226. .br
  227. .sp
  228. A local Unix domain socket connection is defined by the "unix:\fIpath\fR"
  229. format (where "unix:" is the literal character string prefix and \fIpath\fR
  230. is the pathname of the local socket).
  231. .br
  232. .sp
  233. An IPMI Serial-Over-LAN connection is defined by the "ipmi:\fIhost\fR" format
  234. (where "ipmi:" is the literal string and \fIhost\fR is a hostname or IPv4
  235. address).
  236. .br
  237. .sp
  238. The '\fB%N\fR' character sequence will be replaced by the console name.
  239. .TP
  240. \fBlog\fR \fB=\fR "\fIfile\fR"
  241. Specifies the file where console output is logged. This string undergoes
  242. conversion specifier expansion (cf., \fBCONVERSION SPECIFICATIONS\fR) each
  243. time the file is opened. If an absolute pathname is not given, the file's
  244. location is relative to either \fBlogdir\fR (if defined) or the current
  245. working directory. Intermediate directories will be created as needed.
  246. An empty log string (i.e., \fBlog\fR="") disables logging, overriding the
  247. \fBglobal log\fR name.
  248. .TP
  249. \fBlogopts\fR \fB=\fR "\fIstring\fR"
  250. This keyword is optional (cf., \fBGLOBAL DIRECTIVES\fR).
  251. .TP
  252. \fBseropts\fR \fB=\fR "\fIstring\fR"
  253. This keyword is optional (cf., \fBGLOBAL DIRECTIVES\fR).
  254. .TP
  255. \fBipmiopts\fR \fB=\fR "\fIstring\fR"
  256. This keyword is optional (cf., \fBGLOBAL DIRECTIVES\fR).
  257. .SH CONVERSION SPECIFICATIONS
  258. A conversion specifier is a two-character sequence beginning with
  259. a '\fB%\fR' character. The second character in the sequence specifies the
  260. type of conversion to be applied. The following specifiers are supported:
  261. .TP
  262. \fB%N\fR
  263. The console name (from the \fBname\fR string).
  264. .TP
  265. \fB%D\fR
  266. The console device basename (from the \fBdev\fR string),
  267. with leading directory components removed.
  268. .TP
  269. \fB%P\fR
  270. The daemon's process identifier.
  271. .TP
  272. \fB%Y\fR
  273. The year as a 4-digit number with the century.
  274. .TP
  275. \fB%y\fR
  276. The year as a 2-digit number without the century.
  277. .TP
  278. \fB%m\fR
  279. The month as a 2-digit number (01-12).
  280. .TP
  281. \fB%d\fR
  282. The day of the month as a 2-digit number (01-31).
  283. .TP
  284. \fB%H\fR
  285. The hour as a 2-digit number using a 24-hour clock (00-23).
  286. .TP
  287. \fB%M\fR
  288. The minute as a 2-digit number (00-59).
  289. .TP
  290. \fB%S\fR
  291. The seconds as a 2-digit number (00-61).
  292. .TP
  293. \fB%s\fR
  294. The number of seconds since the Epoch.
  295. .TP
  296. \fB%%\fR
  297. A literal '%' character.
  298. .PP
  299. The console name (\fB%N\fR) and device (\fB%D\fR) specifiers are "sanitized"
  300. in that non-printable characters and the forward-slash (/) character are
  301. replaced with underscores.
  302. .SH FILES
  303. .I @CONMAN_CONF@
  304. .SH AUTHOR
  305. Chris Dunlap <cdunlap@llnl.gov>
  306. .SH COPYRIGHT
  307. Copyright (C) 2007-2011 Lawrence Livermore National Security, LLC.
  308. .br
  309. Copyright (C) 2001-2007 The Regents of the University of California.
  310. ConMan is free software: you can redistribute it and/or modify it under
  311. the terms of the GNU General Public License as published by the Free
  312. Software Foundation, either version 3 of the License, or (at your option)
  313. any later version.
  314. .SH "SEE ALSO"
  315. .BR conman (1),
  316. .BR conmand (8).
  317. .PP
  318. \fBhttp://conman.googlecode.com/\fR