Browsing /General Usage/Preferences Window/giftd
- - User Interface Connections
This is the hostname and port number the daemon is listen on to accept connections, This
should normally be you local machine (IP address 127.0.0.1), being 1213
the default port number - Unless you have a special need to use a non-standard port,
just accept the default.
- - Allowed Connections
Space separated list of hosts to allow connection to the daemon (running default on port 1213).
This protocol is used to the communication between daemon and client, and could be considered
a security risk if you allow external connections.
The following special keywords are supported:
- ALL is a synonym for 0.0.0.0/0
- LOCAL is a synonym for 127.0.0.0/8 192.168.0.0/16 22.214.171.124/11 10.0.0.0/8
Bitwidth fields are optional
Command Line Options are options which are passed to giftd by either at the
command line prompt (obviously) or as SystemTags()'s
attributes. options follow explained:
- - Disable Logging
giftd logs several different actions to the logfile
amigift:daemon/giftd.log (mainly for debugging purposes),
enabling this option will cause such log not to be generated.
- - AsyncIO buffer
As above stated, from version 2.0 downloads are saved to disk by
here you can define the write buffer (in bytes!) this library will use.
That buffer size will be used for each of your downloads, meaning if you define here 1000000
and you has 10 active downloads, it will require then 10MB of free RAM.
- - Enable Console Output
This option will let you be able to read interactively the contents of the
amigift:daemon/giftd.log logfile in
a console (eg CON:) window at your Workbench (or public screen).
If you enable the switch you'll have to provide a console window as well (no
default one is available..), also, this option has no effect if logging is
- - Priority
Here you can define at which priority do you want the daemon to be run.
- - Incoming
Directory to store transfers while they are being operated on (downloaded).
Temporary state files are also kept here. It is recommended, but not required, that
the incoming and completed directories are on the same partition (drive),
as above stated.
- - Completed
Directory which will contain files after they have successfully finished downloading.
- - Shares
List of fully qualified paths you wish to share. These directories will be recursed
at giftd's startup and the files contained within will be subjected to an MD5 hashing.
The results will be cached and will only be recalculated on a per share basis when
the size or modification time in the cache and on disk disagree, or the file name
Sanity notice: Do NOT share source directories! Remote nodes will refuse to index
your shares if you are attempting to submit more than 64000 files. - Also note that
under lower powered machines high amount of files being shared (files, not MBs) could
result on lost of connections due the time it could take them to be readed from disk
Security notice: Do not share directories which may contain sensitive information,
such as ENVARC: or S:. - Also note that any directories shared
here will be stripped of all but the last path element when sub-mitted to other
nodes for indexing, effectively "hiding" the directory prefix.
- - Hidden extensions
Space-separated list of extensions whose files will not be shared.
- - Resync Interval
Controls when giFT periodically rescans your shared directories for any changes
(new files, missing files, changed files, etc.) and communicates those
changes to the underlying protocols. This parameter specifies how often
(in seconds) you want that to happen.
For your reference:
- 0 turns off periodic auto-resync
- 3600 one hour
- 86400 one day
- 604800 one week
- - Max Uploads per user
Maximum amount of uploads allowed from the same user at any given time.
It is recommended that you keep this at 1 in order to prevent users from
unfairly queueing your connection.
- - Max Uploads simultaneous
Maximum amount of simultaneous uploads allowed. Setting this to -1 will cause
giftd to not limit outgoing transfers. 0 effectively disables sharing.
- - Hide dot files
Determines whether or not to hide directories which contain a leading dot.
These directories are commonly meant to be "hidden" and thus should not be
submitted to the network.
- - Share Completed
Controls whether or not giftd should automatically share files that you have
finished downloading. This feature significantly improves the networks abudance
of files and helps ease the load on those sharing popular files.
It's a Good Thing (TM), please leave it on.
- - Ignore incoming
Determines whether or not your incoming folder should be shared as well. Normally you
should keep this option un-selected...
- - Shares Hidden
Controls whether or not your list of shares shouldn't be transmitted to the
supernodes (meaning, as a temporal way).
- - Down/up-stream bandwidth
Bandwidth throttling allows AMIGIFT to have some basic control over your bandwidth usage.
This code operates in user space, and as a result can not guarantee perfect accuracy.
If you wish to enable use this feature, please consider using a more reliable
kernel space option first....
The configuration sliders control the maximum number of bytes per second allowed for the
given stream direction. A setting of 0 ('unlimited') will disable throttling for that direction.
- - Reports
This option tells the daemon when it should send transfers progress back to GiFTMui, under
slower systems, it is not recommended to use a lower value than 2 seconds to avoid
overhead... The minimum value for uploads could be even higher, and recommended.
Change Slip controls at which interval should the daemon report transfers progress
when there is no data transfered, so that the GiFTMui's listview gets refreshed.
Also, this is the value interval which states when the #?.state files need to be
written/updated back to disk.
From this page you can select at which p2p networks do you want to connect to.
$Id: index.php,v 2.0 2009/08/06 22:47:32 diegocr Exp $