Changeset 480 for trunk/server/docs-xml/manpages-3/net.8.xml
- Timestamp:
- Aug 2, 2010, 8:16:45 PM (15 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 453,478
- Property svn:mergeinfo changed
-
trunk/server/docs-xml/manpages-3/net.8.xml
r429 r480 1791 1791 1792 1792 <refsect2> 1793 <title>G_LOCK</title> 1794 1795 <para>Manage global locks.</para> 1796 1797 <refsect3> 1798 <title>G_LOCK DO <replaceable>lockname</replaceable> <replaceable>timeout</replaceable> <replaceable>command</replaceable></title> 1799 1800 <para> 1801 Execute a shell command under a global lock. This might be useful to define the 1802 order in which several shell commands will be executed. The locking information 1803 is stored in a file called <filename>g_lock.tdb</filename>. In setups with CTDB 1804 running, the locking information will be available on all cluster nodes. 1805 </para> 1806 1807 <itemizedlist> 1808 <listitem><para><replaceable>LOCKNAME</replaceable> defines the name of the global lock.</para></listitem> 1809 <listitem><para><replaceable>TIMEOUT</replaceable> defines the timeout.</para></listitem> 1810 <listitem><para><replaceable>COMMAND</replaceable> defines the shell command to execute.</para></listitem> 1811 </itemizedlist> 1812 </refsect3> 1813 1814 <refsect3> 1815 <title>G_LOCK LOCKS</title> 1816 1817 <para> 1818 Print a list of all currently existing locknames. 1819 </para> 1820 </refsect3> 1821 1822 <refsect3> 1823 <title>G_LOCK DUMP <replaceable>lockname</replaceable></title> 1824 1825 <para> 1826 Dump the locking table of a certain global lock. 1827 </para> 1828 </refsect3> 1829 1830 </refsect2> 1831 1832 <refsect2> 1793 1833 <title>HELP [COMMAND]</title> 1794 1834
Note:
See TracChangeset
for help on using the changeset viewer.