Revision 73415719 man/gnt-cluster.sgml
b/man/gnt-cluster.sgml | ||
---|---|---|
302 | 302 |
</refsect2> |
303 | 303 |
|
304 | 304 |
<refsect2> |
305 |
<title>SEARCH-TAGS</title> |
|
306 |
|
|
307 |
<cmdsynopsis> |
|
308 |
<command>search-tags</command> |
|
309 |
<arg choice="req"><replaceable>pattern</replaceable></arg> |
|
310 |
</cmdsynopsis> |
|
311 |
|
|
312 |
<para> |
|
313 |
Searches the tags on all objects in the cluster (the cluster |
|
314 |
itself, the nodes and the instances) for a given pattern. The |
|
315 |
pattern is interpreted as a regular expression and a search |
|
316 |
will be done on it (i.e. the given pattern is not anchored to |
|
317 |
the beggining of the string; if you want that, prefix the |
|
318 |
pattern with <literal>^</literal>). |
|
319 |
</para> |
|
320 |
|
|
321 |
<para> |
|
322 |
If no tags are matching the pattern, the exit code of the |
|
323 |
command will be one. If there is at least one match, the exit |
|
324 |
code will be zero. Each match is listed on one line, the |
|
325 |
object and the tag separated by a space. The cluster will be |
|
326 |
listed as <filename>/cluster</filename>, a node will be listed |
|
327 |
as |
|
328 |
<filename>/nodes/<replaceable>name</replaceable></filename>, |
|
329 |
and an instance as |
|
330 |
<filename>/instances/<replaceable>name</replaceable></filename>. |
|
331 |
Example: |
|
332 |
</para> |
|
333 |
<screen> |
|
334 |
# gnt-cluster search time |
|
335 |
/cluster ctime:2007-09-01 |
|
336 |
/nodes/node1.example.com mtime:2007-10-04 |
|
337 |
</screen> |
|
338 |
</refsect2> |
|
339 |
|
|
340 |
<refsect2> |
|
305 | 341 |
<title>VERIFY</title> |
306 | 342 |
|
307 | 343 |
<cmdsynopsis> |
Also available in: Unified diff