Find the answer to your Linux question:
Results 1 to 3 of 3
alright, i jsut read the howto ask questions, so please let me try this again. after spending allot of time woring at and trying to get apollon to work, and ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2004
    Posts
    18

    giftd and giFToxic


    alright, i jsut read the howto ask questions, so please let me try this again.


    after spending allot of time woring at and trying to get apollon to work, and trying a million different things to which none was the answer i gave up, and now ive got both the giftd and giFToxic installed, but i cant seem to get the giFToxic to work.... it sais "gift daemon was started but could not be connected to."

    I figured its cuz i dont have the fast-track plugin..... so i went and got myself a tarball for it... but the tarball is asking for

    "configure: error: Library requirements (libgift >= 0.11.1 libgift < 0.12.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them."

    and i cant find libgift anywhere... ive been searching for 5+hours..... ive only found libgift0, or libgift-dev....I said to myself, maybe libgift0 is libgift.... so i went to the giftd package page on http://packages.debian.org/unstable/net/giftd ... and the requirements say libgift0, now im assuming that libgift0 is libgift.... since they are versioned .11 and .12....... but it sais libgift0>0.12 and the libgift0 that http://packages.debian.org/unstable/net/giftd links you to is 0.11(http://packages.debian.org/unstable/libs/libgift0).... kinda stupid no?[/url]....

    i know that i make allot of assumptions, but i am very new to linux, and have a raggy old unix bible as my only reference material aside from what i can get online (of which there seems to be nothing for giftd).

  2. #2
    Linux User
    Join Date
    Nov 2003
    Location
    Brooklyn, NY
    Posts
    347
    If you do want support for KaZaA you will need FastTrack. I am on gentoo so all I had to do is write one command to get it from the portage, did not even try with the tarball (so you would have to search the answer on this somewhere or get from someone else).

    Code:
    slip@insomnia .giFT $ cat giftd.conf
     
     
    &#91;main&#93;
     
    # Boolean determining whether or not this file has been reviewed and is
    # complete.  giFT will fail to start unless this is non-zero.  This is done
    # so that we can make sure you, at the very least, read through this file.
    # Default&#58; 0
    setup = 1
     
    # Space separated list of hosts to allow connection to giFT's interface
    # protocol &#40;running default on port 1213&#41;.  This protocol is used for GUIs
    # to communicate with giFT and could be considered a security risk to allow
    # external connections.
    # The following special keywords are supported&#58;
    #  ALL       - Synonym for 0.0.0.0/0
    #  LOCAL     - Synonym for 127.0.0.0/8 192.168.0.0/16 172.0.0.0/11 10.0.0.0/8
    # Bitwidth fields are optional.
    # Default&#58; LOCAL
    hosts_allow = LOCAL
     
    # Port on which to listen for user interface connections.  Unless you have a
    # special need to talk to the client on a non-standard port, just accept the
    # default.
    # NOTE&#58;
    #  If you change this value, you will also need to modify the ui.conf
    #  configuration for the machine which will be making outgoing connections
    #  here.
    client_port = 1213
     
    # Determines whether or not to follow symbolic links.  If this value is set
    # non-zero, symlinks will be traversed and a directory inode tracking system
    # will be used to ensure that giFT does not descend the same directory
    # twice.  If you do not have any symlinks or do not want them traversed, set
    # this to 0 for a very minor efficiency gain.
    # Windows users&#58; this setting has no effect.
    # Default&#58; 1
    follow_symlinks = 1
     
    # Colon separated list of protocol plugins to load by default.  If dynamic
    # library support is enabled, the plugin specified will be stat'd to check if
    # it is a loadable path.  If that fails, the fallback method is to attempt to
    # construct the fully qualified path based on the configured environment.
    # NOTES&#58;
    #  Without dynamic library support, this plugin must have been compiled into
    #  your giFT binary.  With, this plugin must exist in the installed
    #  plugin directory.  giFT -V will output this path to you, if you are not
    #  sure.
    #  Protocol names are case sensitive, so use OpenFT, not Openft.
    # For example, to use the OpenFT and Gnutella protocols use&#58;
    #  OpenFT&#58;Gnutella
    # Default&#58; none
    plugins = OpenFT&#58;Gnutella&#58;FastTrack
     
    ###############################################################################
    # DOWNLOAD CONTROLS
     
    &#91;download&#93;
     
    # Directory to store transfers while they are being operated on.  Temporary
    # state files are also kept here.  It is recommended, but not required, that
    # the incoming and completed directories are on the same partition &#40;drive&#41;.
    # Windows users&#58; please use the following path specification&#58;
    # incoming = /C/Program Files/giFT/incoming
    # For example, to refer to C&#58;\Program Files\giFT\incoming, use&#58;
    # incoming = /C/Program Files/giFT/incoming
    # Default &#40;*nix&#41;&#58;    ~/.giFT/incoming
    # Default &#40;Windows&#41;&#58; /C/Program Files/giFT/incoming
    incoming = /files/Download/p2p
     
    # Directory which will contain files after they have successfully finished
    # downloading.
    # Default &#40;*nix&#41;&#58;    ~/.giFT/completed
    # Default &#40;Windows&#41;&#58; /C/Program Files/giFT/completed
    completed = /files/Download/p2p
     
    ###############################################################################
    # SHARE SUBMISSION AND UPLOAD CONTROL
     
    &#91;sharing&#93;
     
    # 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.
    # Default&#58; 1
    max_peruser_uploads = 1
     
    # 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.  Selecting 0 here will submit all directories.
    # Default&#58; 1
    hide_dot_files = 1
     
    # Colon separated list of fully qualified paths you wish to share.  These
    # directories will be recursed at giFT'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 is
    # changed.
    # Sanity notice&#58;
    #  Do NOT share source directories!  Remote nodes will refuse to index your
    #  shares if you are attempting to submit more than 64000 files.
    # Security notice&#58;
    #  Do not share directories which may contain sensitive information, such as
    #  ~ &#40;$HOME&#41;.  Also note that any directories shared here will be stripped of
    #  all but the last path element when submitted to other nodes for indexing,
    #  effectively "hiding" the directory prefix.
    # Windows users&#58; please use the following path specification&#58;
    #  /&#91;drive&#93;/dir1/dir2&#58;/&#91;drive&#93;/dir3/dir4 ...
    # For example, to refer to C&#58;\Program Files\giFT\shares and D&#58;\shares, use&#58;
    #  /C/Program Files/giFT/shares&#58;/D/shares
    # Default&#58; none
    root = none
     
    # Maximum amount of simultaneous uploads allowed.  Setting this to -1 will
    # cause giFT to not limit outgoing transfers.  0 effectively disables sharing.
    # This may also be handled at run time via your GUI of choice.
    # Default&#58; -1
    max_uploads = 0
     
    # Controls when giFT periodically rescans your shared directories for any
    # changes &#40;new files, missing files, changed files, etc.&#41; and communicates
    # those changes to the underlying protocols.  This parameter specifies how
    # often &#40;in seconds&#41; you want that to happen.
    # For your reference
    # 0        turns off periodic auto-resync
    # 3600     one hour
    # 86400    one day
    # 604800   one week
    # Default&#58; 86400
    auto_resync_interval = 86400
     
    # Controls whether or not giFT should automatically share files that you have
    # finished downloading.  This feature significantly improves the network's
    # abundance of files and helps ease the load on those sharing popular files.
    # It's a Good Thing &#40;TM&#41;, please leave it on.
    # Avoid setting your completed directories through sharing/root, as that
    # setting will duplicate recursion of the completed directory and cause
    # generally undesirable results.
    # Default&#58; 1
    share_completed = 1
     
    ###############################################################################
    # USER SPACE BANDWIDTH CONTROL
     
    &#91;bandwidth&#93;
     
    # Bandwidth throttling allows giFT 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 use this feature, please
    # consider using a more reliable kernel space option first.  As always, google
    # should be able to assist you there.
    # The following configuration switches control the maximum number of bytes
    # per second allowed for the given stream direction.  A setting of 0 will
    # disable throttling for that direction.
    # Default&#58; 0
    downstream = set the speed
    upstream = 5120
    After you configured giFT, you simply run
    Code:
    slip@insomnia slip $ giftd -d
    &#91;06&#58;08&#58;53&#93; giFT&#58; 18108
    slip@insomnia slip $
    And start any client you want.. Apollon or giFToxic or whatever you want.

  3. #3
    Just Joined!
    Join Date
    Jun 2004
    Posts
    11

    configuring gift

    With my last installation, I remember, that I configured the gift as you showed. But now I can't. Console always write back:

    "command not found"

    Why? I have Suse 9.1. As I remember, the command I used in the past is gift.setup or giftsetup or something like that. But I tried them all, plus what you showed, but nothing!
    Without configuring, I can not use the Gnutella.
    Pleeeease help!!!!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •