trickle(1) [debian man page]

TRICKLE(1)						    BSD General Commands Manual 						TRICKLE(1)

NAME

     trickle -- a lightweight userspace bandwidth shaper

SYNOPSIS

     trickle [-h] [-v] [-V] [-s] [-d rate] [-u rate] [-w length] [-t time] [-l length] [-n path] [-P path] command ...

DESCRIPTION

     trickle is a userspace bandwidth manager.	Currently, trickle supports the shaping of any SOCK_STREAM (see socket(2)) connection established
     via the socket(2) interface.  Furthermore, trickle will not work with statically linked executables, nor with setuid(2) executables.  trickle
     is highly configurable; download and upload rates can be set separately, or in an aggregate fashion.

     The options are as follows:

     -h 	  Displays help.

     -v 	  Increases the verbosity level (can be specified multiple times).

     -V 	  Prints version.

     -s 	  Runs trickle in standalone mode, independent of trickled(8).

     -d rate	  Limit the download bandwidth consumption to rate KB/s.

     -u rate	  Limit the upload bandwidth consumption to rate KB/s.

     -w length	  Set peak detection window size to length KB.	This determines how aggressive trickle is at eliminating bandwidth consumption
		  peaks.  Lower values will be more aggressive, but may also result in over shaping.  The default value (512 KB) is usually suffi-
		  cient.

     -t seconds   Set smoothing time to seconds s.  The smoothing time determines with what intervals trickle will try to let the application
		  transceive data.  Smaller values will result in a more continuous (smooth) session, while larger values may produce bursts in
		  the sending and receiving data.  Smaller values (0.1 - 1 s) are ideal for interactive applications while slightly larger values
		  (1 - 10 s) are better for applications that need bulk transfer.

     -l length	  Set smoothing length to length KB.  The smoothing length is a fallback of the smoothing time.  If trickle cannot meet the
		  requested smoothing time, it will instead fall back on sending length KB of data.  The default value is 10 KB.

     -n path	  Use trickled(8) socket path to communicate with trickled(8).	By default, /tmp/.trickled.sock is used.

     -P path	  Use the specified .so instead of the standard one, this is usefull if you don't run trickle from a standard installation.

EXAMPLES

     trickle -u 10 -d 20 ncftp

     Launch ncftp(1) limiting its upload capacity to 10 KB/s, and download capacity at 20 KB/s.

SEE ALSO

     trickled(8), syslog(3), socket(2), netintro(4)

AUTHORS

     trickle has been developed by Marius Aamodt Eriksen <marius@monkey.org>.

BUGS

     Does not support executables utilizing kqueue(2).	Does not support statically linked executables.

BSD
								 November 10, 2002							       BSD

FLUSH(1)						      General Commands Manual							  FLUSH(1)

NAME

       Flush - GTK-based BitTorrent client

SYNOPSIS

       flush [OPTIONS] [TORRENT_FILE]...

DESCRIPTION

       Flush is a GTK-based BitTorrent client. You can use it to download files from the BitTorrent network.

       You can control already running instance, for example, by following commands:
	      flush -o --download-rate-limit=100
	      flush --start=all

FEATURES

       * Controlling running instance by command line interface, such as:
	 * Starting/stopping torrents.
	 * Changing download/upload rate limit.
	 * Changing maximum connections limit.
       * Running many instances with different configs from the same user.
       * Automatic copying finished downloads to specified directory.
       * Setting custom download path for each file of the torrent.
       * Ability to choose torrent file's character set encoding.
       * Automatic torrents loading from specified directory.
       * Automatic pausing and removing old torrents.
       * Temporary pausing and resuming torrents.
       * Overall and current session statistics.
       * Creating your own torrent files.
       * IP filter.

OPTIONS

       --version
	      Show program version and exit.

       --help Show help options and exit.

       --config=DIRECTORY
	      Configuration directory path (default: ~/.flush).

       --download-rate-limit=SPEED
	      Set download rate limit (KB/s).

       --upload-rate-limit=SPEED
	      Set upload rate limit (KB/s).

       --max-uploads=NUMBER
	      Set maximum uploads.

       --max-connections=NUMBER
	      Set maximum connections.

       --start={all,downloads,uploads}
	      Start torrents.

       --stop={all,downloads,uploads}
	      Stop torrents.

       -o, --only-pass
	      Only pass commands to already running Flush instance. Does not start new instance if it is not running yet.

FILES

       ~/.flush
	      Default configuration directory.

BUGS

       On  startup  Flush  finds  already  running  instances via DBus session bus. Therefore it is necessary to run Flush in a single session bus
       (usual in X session bus) to prevent running several instances with one configuration path.

       Please notice that when you are running Flush from console or by cron, when DISPLAY environment variable  is  not  available,  Flush  finds
       already	running  GUI  instance	without problems via ${config_path}/dbus_session link, which all GUI instances are creating when they have
       owned DBus name. This makes it possible to control running Flush GUI instances from cron.

AUTHOR

       Flush was written by Dmitry Konishchev <konishchev@gmail.com>.
       This manual page was written by Dmitry Konishchev <konishchev@gmail.com>.

								   Jun 11, 2009 							  FLUSH(1)