Your IP : 216.73.216.48


Current Path : /usr/X11R6/share/epic5/help/1_General/dcc/
Upload File :
Current File : //usr/X11R6/share/epic5/help/1_General/dcc/close

# $EPIC: close,v 1.4 2003/07/07 05:24:17 jnelson Exp $
Synopsis:
   dcc close [<type>|-all|*] [<nick>|-all|*] ["<filename>"]

Description:
   DCC CLOSE cancels a DCC session:
   * For DCC SEND, it rescinds the offer to send a file
   * For DCC GET, it rejects our interest in receiving the file
   * For DCC CHAT, it closes the dedicated chat connection
   * For $connect(), it closes the raw client socket connection
   * For $listen(), it closes the listening socket (but not any connections)
   * For a file transfer in progress, it terminates the transfer early.

   The <type> argument is one of:
	CHAT	for private one-to-one conversations
	SEND	for outbound file transfers
	GET	for inbound file transfers
	RAW	for $connect()s or $listen()s
	-ALL	for all DCCs of all of the above types
	*	same as -ALL

   The <nick> argument is the name of the peer, as shown in the DCC LIST
   output.  It may be -ALL or * to match all DCCs of the given <type>.

   <filename> may be in double quotes, if it contains spaces.  <filename>
   is only necessary for DCC SEND or DCC GET connections.

   If you do not provide <filename> and there are multiple connections of
   a given <type> to <nick> open, the first such connection is closed.

   There is no wildcard support for <type>, <nick>, or <filename>.

   When you DCC CLOSE a pending connection (either an offer you have
   made to someone else, or an offer someone has made to you, but which
   has not been accepted), it is considered a DCC REJECT and a CTCP
   reply to the other peer will be send to notify them the connection
   will not be completed.

   If someone is sending you a file, you want to DCC CLOSE GET <nick> and 
   if you are sending someone a file, you want to DCC CLOSE SEND <nick>.
   
   If you exit the client, all of your open DCC connections are closed.

   On some older versions of EPIC, doing DCC CLOSE from within an ON
   related to a DCC event could cause a crash.  Be careful about closing
   a DCC that is currently being processed.

Examples:
   To close an existing DCC CHAT connection with bob:
      /dcc close chat bob

   To reject an incoming DCC SEND connection from bob:
      /dcc close get bob

   To close all DCC CHAT connections:
      /dcc close chat *
         or
      /dcc close chat -all

    To close all DCC connections with or offered by bob:
      /dcc close * bob
         or
      /dcc close -all bob

History:
   The DCC CLOSE command first appeared in ircII-2.1.2

See Also:
   dcc(1) closeall, list, rename; on(5) dcc_lost