diff options
author | Christopher Faylor <me@cgf.cx> | 2001-11-12 03:14:27 +0300 |
---|---|---|
committer | Christopher Faylor <me@cgf.cx> | 2001-11-12 03:14:27 +0300 |
commit | 71f90de808505e23c9c28451956742ac362c9ec7 (patch) | |
tree | 703ff5445b6db4820c7ceea4f84a06382ffed082 /winsup/utils/utils.sgml | |
parent | 7d3480deef4f9d00215d0326c531ce58cd56478c (diff) |
* cygcheck.cc (scan_registry): Open registry with read-only access.
(main): Reflect argument change for dump_setup.
* dump_setup.cc (dump_setup): Add preliminary extra argument for future use.
* path.cc (read_mounts): Open registry with read-only access.
Diffstat (limited to 'winsup/utils/utils.sgml')
-rw-r--r-- | winsup/utils/utils.sgml | 26 |
1 files changed, 17 insertions, 9 deletions
diff --git a/winsup/utils/utils.sgml b/winsup/utils/utils.sgml index 1f25c3423..9caa44bf3 100644 --- a/winsup/utils/utils.sgml +++ b/winsup/utils/utils.sgml @@ -9,6 +9,7 @@ specifically for Cygwin.</para> <screen> Usage: cygcheck [-s] [-v] [-r] [-h] [program ...] + -c = check current package setup -s = system information -v = verbose output (indented) (for -s or programs) -r = registry search (requires -s) @@ -27,6 +28,11 @@ option, it will give general system information. If you specify <literal>-s</literal> and list one or more programs on the command line, it reports on both.</para> +<para>The <literal>-c</literal> option causes the "program" arguments +to be interpreted as package names. <command>cygcheck</command> will +report the current version of the package that you specify. With no +arguments, <command>cygcheck</command> will report on all packages. + <para>The <command>cygcheck</command> program should be used to send information about your system to Cygnus for troubleshooting (if your support representative requests it). When asked to run this command, @@ -120,7 +126,7 @@ done <sect2 id="kill"><title>kill</title> <screen> -Usage: kill [-sigN] pid1 [pid2 ...] +Usage: kill [-f] [-sigN] pid1 [pid2 ...] </screen> <para>The <command>kill</command> program allows you to send arbitrary @@ -130,20 +136,22 @@ also send program-specified signals such as SIGUSR1 to trigger actions within the program, like enabling debugging or re-opening log files. Each program defines the signals they understand.</para> -<para>Note that the "pid" values are the Cygwin pids, not the Windows -pids. To get a list of running programs and their Cygwin pids, use -the Cygwin <command>ps</command> program.</para> +<para>Note that, unless you specific the <literal>-f</literal> option, +the "pid" values are the Cygwin pids, not the Windows pids. To get a +list of running programs and their Cygwin pids, use the Cygwin +<command>ps</command> program. <command>ps -W</command> will display +<emphasis>all</emphasis> windows pids.</para> -<para>To send a specific signal, use the -<literal>-signN</literal> option, either -with a signal number or a signal name (minus the "SIG" part), like -these examples:</para> +<para>To send a specific signal, use the <literal>-signN</literal> +option, either with a signal number or a signal name (minus the "SIG" +part), like these examples:</para> -<example><title>Specifying signals with the kill command</title> +<example><title>Using the kill command</title> <screen> <prompt>$</prompt> <userinput>kill 123</userinput> <prompt>$</prompt> <userinput>kill -1 123</userinput> <prompt>$</prompt> <userinput>kill -HUP 123</userinput> +<prompt>$</prompt> <userinput>kill -f 123</userinput> </screen> </example> |