old-www/LDP/nag/node271.html

36 lines
1.4 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>sendsys, version, and senduuname</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node272.html">C-News in an NFS </A>
<B>Up:</B> <A HREF="node267.html">Control Messages</A>
<B> Previous:</B> <A HREF="node270.html">The checkgroups Message</A>
<BR> <P>
<H2><A NAME="SECTION0019840000">sendsys, version, and senduuname</A></H2>
<A NAME="cnewscontrolsendsys"></A>
<A NAME="cnewscontrolversion"></A>
<A NAME="cnewscontroluuname"></A>
Finally, there are three messages that may be used to find out about the
network's topology. These are sendsys, version, and
senduuname. They cause C-News to return to the sender the
sys file, a software version string, and the output of
uuname(1), respectively. C-News is very laconic about
version messages; it returns a simple, unadorned ``C''.
<P>
Again, you should <em>never</em> issue such a message, unless you have made
sure that it cannot leave a your (regional) network. Replies to
sendsys messages can quickly bring down a UUCP
network.<A HREF="footnode.html#9429"><IMG ALIGN=BOTTOM ALT="gif" SRC="foot_motif.gif"></A>
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>