| /openbsd-src/usr.bin/ssh/ |
| H A D | ssh_config.5 | 7 .\" can be used freely for any purpose. Any derived versions of this
8 .\" software must be clearly marked as such, and if the derived work is
9 .\" incompatible with the protocol description in the RFC file, it must be
28 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
60 will be used.
71 host-specific declarations should be given near the beginning of the
78 Arguments may optionally be enclosed in double quotes
81 Configuration options may be separated by whitespace or
102 keyword) to be only for those hosts that match one of the patterns
104 If more than one pattern is provided, they should be separate
[all...] |
| H A D | sshd_config.5 | 7 .\" can be used freely for any purpose. Any derived versions of this
8 .\" software must be clearly marked as such, and if the derived work is
9 .\" incompatible with the protocol description in the RFC file, it must be
28 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
51 Unless noted otherwise, for each keyword, the first obtained value will be used.
55 Arguments may optionally be enclosed in double quotes
64 Specifies what environment variables sent by the client will be copied into
82 Multiple environment variables may be separated by whitespace or spread
86 Be warned that some environment variables could be use
[all...] |
| /openbsd-src/gnu/usr.bin/texinfo/makeinfo/tests/ |
| H A D | accent-text.txi | 3 should be e`: @`{e} @`e
5 should be e': @'{e} @'e
7 should be e^: @^{e} @^e
9 should be u": @"{u} @"u
11 should be i`: @`{i} @`i
13 should be i': @'{i} @'i
15 should be i^: @^{i} @^i
17 should be u": @"{u} @"u
19 should be c,: @,{c} @,c
21 should be n~: @~{n} @~n
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/config/i386/ |
| H A D | beos-elf.h | 11 GNU CC is distributed in the hope that it will be useful,
104 /* ??? This is gonna be lovely when the next release of gcc has
149 { "/boot/develop/headers/be/add-ons/graphics", 0, 0, 0 },\
150 { "/boot/develop/headers/be/devel", 0, 0, 0 },\
151 { "/boot/develop/headers/be/translation", 0, 0, 0 },\
152 { "/boot/develop/headers/be/mail", 0, 0, 0 },\
154 { "/boot/develop/headers/be/drivers", 0, 0, 0 },\
155 { "/boot/develop/headers/be/opengl", 0, 0, 0 },\
156 { "/boot/develop/headers/be/game", 0, 0, 0 },\
157 { "/boot/develop/headers/be/support", 0, 0, 0 },\
[all …]
|
| /openbsd-src/gnu/gcc/gcc/config/i386/ |
| H A D | beos-elf.h | 12 GCC is distributed in the hope that it will be useful,
100 /* ??? This is gonna be lovely when the next release of gcc has
145 { "/boot/develop/headers/be/add-ons/graphics", 0, 0, 0 },\
146 { "/boot/develop/headers/be/devel", 0, 0, 0 },\
147 { "/boot/develop/headers/be/translation", 0, 0, 0 },\
148 { "/boot/develop/headers/be/mail", 0, 0, 0 },\
150 { "/boot/develop/headers/be/drivers", 0, 0, 0 },\
151 { "/boot/develop/headers/be/opengl", 0, 0, 0 },\
152 { "/boot/develop/headers/be/game", 0, 0, 0 },\
153 { "/boot/develop/headers/be/support", 0, 0, 0 },\
[all …]
|
| /openbsd-src/usr.sbin/dhcpd/ |
| H A D | dhcpd.conf.5 | 16 .\" of its contributors may be used to endorse or promote products derived
24 .\" CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
59 Comments may be placed anywhere within the file (except within quotes).
75 can be assigned to clients, or to apply a group of parameters to a
77 In any group of parameters and declarations, all parameters must be specified
78 before any declarations which depend on those parameters may be specified.
85 If clients on a subnet are to be assigned addresses dynamically, a
91 only known clients will be served, each such client must have a
94 If parameters are to be applied to a group of declarations which are not
97 declaration can be used.
[all …]
|
| /openbsd-src/gnu/usr.sbin/mkhybrid/src/ |
| H A D | mkisofs.8 | 150 must be different from the other filenames in the same directory.
159 number as an extension (where the number is guaranteed to be unique). An
160 example of this would be the files foo.bar and
161 foo.bar.~1~ - the file foo.bar.~1~ would be written as FOO.000;1 and the file
162 foo.bar would be written as FOO.BAR;1
195 that you be able to maintain an uninterrupted data stream to the writer
200 is the path of the directory tree to be copied into the iso9660 filesystem.
201 Multiple paths can be specified, and
221 same sort of syntax can be used with directories as well.
226 fly like this will have permissions 0555 and appear to be owned by the
[all …]
|
| H A D | mkhybrid.8 | 283 must be different from the other filenames in the same directory.
292 number as an extension (where the number is guaranteed to be unique). An
293 example of this would be the files foo.bar and
294 foo.bar.~1~ - the file foo.bar.~1~ would be written as FOO.000;1 and the file
295 foo.bar would be written as FOO.BAR;1
338 that you be able to maintain an uninterrupted data stream to the writer
344 is the path of the directory tree to be copied into the iso9660 filesystem.
345 Multiple paths can be specified, and
365 same sort of syntax can be used with directories as well.
371 fly like this will have permissions 0555 and appear to be owned by the
[all …]
|
| /openbsd-src/usr.bin/dig/lib/dns/include/dns/ |
| H A D | message.h | 10 * AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
42 * signatures should also be checked here.
49 * Names and rdatasets must be put back into the dns_message_t in
60 * dns_message_gettemp*() will always be freed automatically
63 * to be reused multiple times during the lifetime of the message; offsets
64 * cannot be reused.
66 * Buffers allocated using isc_buffer_allocate() can be automatically freed
68 * Doing this will cause the buffer to be freed using isc_buffer_free()
71 * of code can be written:
119 * Ordering here matters. DNS_SECTION_ANY must be th
[all...] |
| /openbsd-src/usr.sbin/bgpd/ |
| H A D | bgpd.conf.5 | 13 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
36 User-defined variables may be defined and used later, simplifying the
44 Networks which should be announced by
61 the sections should be grouped and appear in
65 The current line can be extended over multiple lines using a backslash
67 Comments can be put anywhere in the file using a hash mark
70 Care should be taken when commenting out multi-line text:
74 must be quoted.
76 Additional configuration files can be included with the
83 Macros can be define
[all...] |
| /openbsd-src/gnu/lib/libstdc++/libstdc++/docs/doxygen/ |
| H A D | user.cfg.in | 3 # This file describes the settings to be used by the documentation system
6 # All text after a hash (#) is considered a comment and will be ignored
9 # For lists items can also be appended using:
11 # Values that contain spaces should be placed between quotes (" ")
29 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
30 # This could be handy for archiving the generated documentation or
36 # base path where the generated documentation will be put.
37 # If a relative path is entered, it will be relative to the location
38 # where doxygen was started. If left blank the current directory will be used.
55 # Private class members and static file members will be hidden unless
[all …]
|
| /openbsd-src/usr.sbin/cron/ |
| H A D | crontab.5 | 14 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
35 There may be a system
41 will be
50 is a text file, it is not intended to be directly edited.
53 should be done using
63 they will be taken to be part of the command.
85 will be part of the value assigned to
89 string may be placed in quotes
121 The command may be one or more fields long.
150 A random value for a field may be obtained using the
[all …]
|
| /openbsd-src/share/man/man5/ |
| H A D | port-modules.5 | 19 .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT,
74 Some core modules are a single word, all other modules should be
94 a module will be global to the ports framework, and thus may interfere
99 should be named
106 internal variables and targets not intended for user consumption should be
112 For instance, if a module wants some value to be available for the rest
131 variables will usually drop the version suffix and be simply called
133 so that a port using the module can be switched from version to version
156 to be needed were added.
157 If several modules define the same hook, hook behaviors will be
[all …]
|
| /openbsd-src/lib/libc/stdio/ |
| H A D | wscanf.3 | 19 .\" may be used to endorse or promote products derived from this software
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
122 Scanning also stops when an input conversion cannot be made (see below).
126 character, introducing a conversion, there may be a number of
135 Indicates that the conversion will be one of
144 Indicates that the conversion will be one of
153 Indicates that the conversion will be one of
161 that the conversion will be one of
167 or that the conversion will be one of
176 Indicates that the conversion will be one of
[all …]
|
| /openbsd-src/lib/libelf/ |
| H A D | elf_update.3 | 15 .\" are disclaimed. in no event shall Joseph Koshy be liable
51 can be one of the following values:
63 should permit the underlying ELF object to be written or updated
74 should be considered invalid after a call to
88 The ELF executable header will be placed at the start of the object.
90 If the ELF descriptor contains a program header table, it will be
93 ELF section data, if any, will be placed next, keeping each section's
96 The ELF section header table, if any, will be placed last.
109 The ELF executable header will be placed at the start of the object.
111 The ELF program header table, if any, it will be placed at the offset
[all …]
|
| /openbsd-src/lib/libz/ |
| H A D | compress.3 | 6 .\" warranty. In no event will the authors be held liable for any damages
13 .\" The origin of this software must not be misrepresented; you must not
15 .\" in a product, an acknowledgment in the product documentation would be
17 .\" Altered source versions must be plainly marked as such, and must not be
19 .\" This notice may not be removed or altered from any source distribution.
266 but other algorithms will be added later and will have the same
269 Compression can be done in a single step if the buffers are large enough
270 or can be done by repeated calls of the compression function.
293 The zlib format was designed to be compac
[all...] |
| /openbsd-src/share/termtypes/ |
| H A D | termcap.5 | 15 .\" may be used to endorse or promote products derived from this software
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
60 The last name given should be a long name fully identifying the terminal,
62 All names but the last should be in lower case and contain no blanks;
67 should be chosen using the following conventions.
72 Modes that the hardware can be in
74 should be indicated by appending a hyphen and an indicator of the mode.
77 in 132-column mode would be
80 The following suffixes should be used where possible:
99 P Indicates that padding may be specified.
[all …]
|
| /openbsd-src/usr.sbin/acme-client/ |
| H A D | acme-client.conf.5 | 14 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
32 User-defined variables may be defined and used later, simplifying the
35 Certificate authorities (CAs) that can be contacted via ACME.
40 Additional configuration files can be included with the
47 The current line can be extended over multiple lines using a backslash
49 Comments can be put anywhere in the file using a hash mark
52 Care should be taken when commenting out multi-line text:
56 must be quoted.
58 Macros can be defined that will later be expanded in context.
61 Macro names may not be reserved words.
[all …]
|
| /openbsd-src/usr.bin/telnet/ |
| H A D | telnet.1 | 16 .\" may be used to endorse or promote products derived from this software
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
113 This can be useful when connecting to services which use IP addresses
141 there will be no escape character.
155 will be sent to the remote system as the value for the variable USER.
159 This option may also be used with the
172 will be written.
175 then tracing information will be written to standard output (the default).
185 Set the routing table to be used.
221 editing or character echoing is to be disabled, the remote system
[all …]
|
| /openbsd-src/gnu/llvm/lldb/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
6 # All text after a hash (#) is considered a comment and will be ignored
9 # For lists items can also be appended using:
11 # Values that contain spaces should be placed between quotes (" ")
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
38 # If a relative path is entered, it will be relative to the location
39 # where doxygen was started. If left blank the current directory will be used.
46 # Enabling this option can be useful when feeding doxygen a huge amount of
[all …]
|
| /openbsd-src/usr.bin/nc/ |
| H A D | nc.1 | 14 .\" 3. The name of the author may not be used to endorse or promote products
20 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
110 Cannot be used together with any of the options
139 Cannot be used with
150 and cannot be used with
180 Cannot be used together with any of the options
196 If a name cannot be resolved without DNS, an error will be reported.
200 During the TLS handshake, load data to be stapled from
210 If no username is specified then authentication will not be attempted.
216 Cannot be used together with
[all …]
|
| /openbsd-src/lib/libc/sys/ |
| H A D | ptrace.2 | 54 can be:
58 that the process expects to be traced by its parent.
61 probably be rather confused by the results; once the traced process stops,
62 it cannot be made to continue except via
73 be ignored.
92 space) at which the read is to be done.
103 may be necessary to ensure that instruction caches are flushed appropriately.
106 argument supplies the value to be written.
114 .\" user structure; it will usually be an integer value cast to
123 .\" must be aligne
[all...] |
| /openbsd-src/lib/libevent/ |
| H A D | event.3 | 12 .\" 2. The name of the author may not be used to endorse or promote products
18 .\" THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
174 API needs to be initialized with
176 before it can be used.
187 to be used in future calls to
191 The event will be prepared to call the function specified by the
204 indicates the file descriptor that should be monitored for events.
205 The events can be either
214 will be called with the file descriptor that triggered the event and
215 the type of event which will be either
[all …]
|
| /openbsd-src/gnu/lib/libstdc++/libstdc++/docs/html/17_intro/ |
| H A D | DESIGN | 6 to projects to be done and how they fit into the whole.
33 with current compilers must be included in-line, resulting in
38 porting. Iostream/locale is (or will be) as large again.
56 to the executable file even when they manifestly cannot be called.
66 What can be done to eliminate this overhead? A variety of coding
68 extensions may be used, as covered below. Most are not difficult,
85 can be placed (once) in a "repository" -- really just a library, but
86 of template definitions rather than object code -- to be drawn upon
88 header files to be parsed along with every compilation unit.
95 To be precise, this means that certain headers which define
[all …]
|
| /openbsd-src/gnu/gcc/libstdc++-v3/docs/html/17_intro/ |
| H A D | DESIGN | 6 to projects to be done and how they fit into the whole.
33 with current compilers must be included in-line, resulting in
38 porting. Iostream/locale is (or will be) as large again.
56 to the executable file even when they manifestly cannot be called.
66 What can be done to eliminate this overhead? A variety of coding
68 extensions may be used, as covered below. Most are not difficult,
85 can be placed (once) in a "repository" -- really just a library, but
86 of template definitions rather than object code -- to be drawn upon
88 header files to be parsed along with every compilation unit.
95 To be precise, this means that certain headers which define
[all …]
|