how to run the GiFT frontend ?

stagnant7 · 04-11-2004, 12:55 AM

[slackware linux 9.1]

Hi There.....

I have installed:
giFT
giFTui (frontend for giFT)
giFT FastTrack
giFT OpenFT
giFT Gnutella

i have run gift-setup and am happy with it

i read somewhere that to run giFT u do the following in a terminal:
giftd -d
then run the frontend (graphical user interface).

when i run giftd -d i get the following returned:
[15:49:50] giFT: 9939

seems ok i guess, teh time connected and whateva 9939 means

but i dont know how to start the graphical interface.....i type in:
giftui (i assume this is what i type??)....and i get the following:
giftui : No host to connect /apps/giftui/daemon/host.

can anyone help me start my GUI?

BTW: I installed all these using slackware's installpkg feature...as i was lucky enough to find slackware packages on the web.

mrcheeks · 04-11-2004, 01:11 AM

giftd&(If you've already configured gift)
giFTui&

stagnant7 · 04-11-2004, 01:55 AM

thanks for the reply...

however i am still having difficulties here is the code i types in the terminal:

Code:

bash-2.05b$ giftd&
[1] 10074
*** GIFT-FATAL: Failed to load interface subsystem
 
NOTE:
There may be another giFT daemon running on this host.  Check to see if the
interface port (1213) is currently in use by another process.
 
bash-2.05b$ *** Often times more information can be found in the log file or with the -v command line switch.
giFTui&
[2] 10075
[1]   Done                    giftd
bash: giFTui: command not found
bash-2.05b$

as u can see i tried both giftd& and giFTui&....am i doing this wrong or is it something more complex?

thanks for any replies

bouke · 04-11-2004, 02:46 AM

Quote:

Originally posted by stagnant7
[B]thanks for the reply...

however i am still having difficulties here is the code i types in the terminal:

[CODE]bash-2.05b$ giftd&
[1] 10074
*** GIFT-FATAL: Failed to load interface subsystem

NOTE:
There may be another giFT daemon running on this host. Check to see if the
interface port (1213) is currently in use by another process.

The Daemon tells you that there is an other giFT Daemon running... Try the command top to check that and kill it.

Try to start the daemon with: giftd -d (that's standard to run it in the background).

Quote:

when i run giftd -d i get the following returned:
[15:49:50] giFT: 9939

9939 is the procesnumber. You are able to kill it with the following command: kill 9939 (it stops the daemon).

Quote:

but i dont know how to start the graphical interface.....i type in:
giftui (i assume this is what i type??)....and i get the following:
giftui : No host to connect /apps/giftui/daemon/host.

Please open your ~/.giFT/giftd.conf in your favorite text-editor and check your client_port. It has to be 1213.

An other option is to (re-)run the command: gift-setup

If this doesn't help it could be that your GUI (giFTui) gives the problem. Just try giFTcurs (it is very easy to compile and works in an terminal). An other GUI is giFToxic (also works fine over here). You'll find them at http://gift.sourceforge.net/ //-> there's also documentation at that location

stagnant7 · 04-11-2004, 03:08 AM

hi thanks for the great info

so i have started typed in giftd -d and all is well:

bash-2.05b$ giftd -d
[18:00:02] giFT: 1281

then i typed giftui and this is what happened:

bash-2.05b$ giftui
giftui : No host to connect /apps/giftui/daemon/host.

hmmm....

btw this was after i re-did the gift-setup..... and ensured i was using 1213. Also i don't know what is meant by ~/.giFT/giftd.conf where is this exactly ??

any further ideas....should i just try another frontend ....what one is similar to giftui cos i rekon i like the look of this one....

thanks for all the help mrcheeks and bouke

bouke · 04-11-2004, 03:26 AM

Quote:

btw this was after i re-did the gift-setup..... and ensured i was using 1213. Also i don't know what is meant by ~/.giFT/giftd.conf where is this exactly ??

With tilde (~) I mean your home-directory (for example /home/username/). You'll find giftd.conf in /home/username/.giFT/

Please ensure that /home/username/.giFT/OpenFT/OpenFT.conf exists. It couldn't be created by the giFT Daemon on my system.

I copied all the files in /usr/local/share/giFT/OpenFT/ to /home/username/.giFT/OpenFT/ (being root). After that I chown-ed these files so I have rights to use them.

An other thing: please update your node-file. There's an example at: http://reviewed.homelinux.org/software/p2p/p2p.html.en

Please enter your username in the example-paths above.

Hope this helps :)

Bouke's giftd.conf

Quote:

# $Id: giftd.conf.template,v 1.2 2003/12/12 12:15:49 jasta Exp $
###############################################################################

###############################################################################
# MAIN

[main]

#
# 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: 0
#
setup = 1

#
# Space separated list of hosts to allow connection to giFT's interface
# protocol (running default on port 1213). 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:
#
# 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: 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:
# 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: this setting has no effect.
#
# Default: 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:
# 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:
#
# OpenFT:Gnutella
#
# Default: none
#
plugins = OpenFT:Gnutella:FastTrack

###############################################################################
# DOWNLOAD CONTROLS

[download]

#
# 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 (drive).
#
# Windows users: please use the following path specification:
#
# incoming=/[drive]/dir1/dir2
#
# For example, to refer to C:\Program Files\giFT\incoming, use:
#
# incoming=/C/Program Files/giFT/incoming
#
# Default (*nix): ~/.giFT/incoming
# Default (Windows): /C/Program Files/giFT/incoming
#
incoming = /shared/Downloads/Incoming

#
# Directory which will contain files after they have successfully finished
# downloading.
#
# Default (*nix): ~/.giFT/completed
# Default (Windows): /C/Program Files/giFT/completed
#
completed = /shared/Downloads

###############################################################################
# SHARE SUBMISSION AND UPLOAD CONTROL

[sharing]

#
# 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: 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: 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:
# 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:
# Do not share directories which may contain sensitive information, such as
# ~ ($HOME). 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: please use the following path specification:
#
# /[drive]/dir1/dir2:/[drive]/dir3/dir4 ...
#
# For example, to refer to C:\Program Files\giFT\shares and D:\shares, use:
#
# /C/Program Files/giFT/shares:/D/shares
#
# Default: none
#
root = /shared/Music:/shared/Other:/shared/Video

#
# 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: -1
#
max_uploads = 3

#
# 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
#
# Default: 86400
#
auto_resync_interval = 21600

#
# 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 (TM), 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: 1
#
share_completed = 1

###############################################################################
# USER SPACE BANDWIDTH CONTROL

[bandwidth]

#
# 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: 0
#
downstream = 0
upstream = 8192

Bouke's OpenFT.conf

Quote:

# $Id: OpenFT.conf.template,v 1.10 2003/12/23 04:31:39 jasta Exp $
###############################################################################

###############################################################################
# MAIN

[main]

#
# Node classification. This value is very important and will determine your
# potential role on the network. The following settings are allowed:
#
# 1 (USER)
#
# Basic class that all nodes implicitly belong to. This node will maintain
# very few TCP connections on the network and perform almost no tasks other
# than to upload to other users. Users who do not have direct Internet
# connections will be forced into this class.
#
# 3 (SEARCH)
#
# Responsible for manging indexes of a large group of directly connected
# children (run-time modifier for the USER class), responding to and
# forwarding search requests from peers, as well as directing push requests
# so that indirectly connected users may still share files.
#
# Please note that this class will require a much greater amount of both
# local and network resources. If you select this, pay very close attention
# to the database environment settings several configuration options down.
# For reference, there are several fully functioning search nodes on
# "average" broadband connections, such as 768/128kbit (my node *sigh*).
#
# Keeping your node up-to-date is absolutely essential for this node class.
# Please check for regular updates and be sure that you are always running
# the latest version.
#
# 5 (INDEX)
#
# Meta node used in favor of user nodes when attempting new connections to
# the network. This node class is also responsible for managing statistics
# information for the virtual clusters created by SEARCH nodes. Reliability
# is the largest requirement here.
#
# If you're unsure it is highly recommended that you select 1 (the default).
# A setting of 7 will select both a SEARCH and INDEX node.
#
class = 1

#
# Core listening port. OpenFT uses a compacted binary protocol for the core
# communication with other nodes. If this machine is unable to provide both
# port and http_port to the outside directly (blocked by either by a firewall
# or a NAT setup) you should select 0 here.
#
# NOTE:
# If you are unable to route this port (along with the HTTP port) you will be
# unable to download from other users with that same inability. You will,
# however, maintain the ability to upload to other non-firewalled users.
# Selecting non-zero when the port is not available to the outside will cause
# very broken behaviour, namely search results will be extremely unreliable.
#
# Default: random (1215, 2215)
#
port = 1215

#
# HTTP server port. OpenFT's implementation also makes use of HTTP for all
# file transfers. See above for more details. Please provide a valid port
# here regardless of your firewall state.
#
# Default: random (2216, 3216)
#
http_port = 2215

#
# Arbitrary name you'd like to associate with your node. This field is
# optional and it is NOT to be trusted. The name is not unique to the
# network. Please do not choose useless aliases.
#
alias = 30uke@ictpc201

###############################################################################
# SEARCH NODE SETTINGS

[connections]

#
# Maximum number of "active" nodes that are allowed connection at any given
# time. The default value (-1) is used to calculate a suitable value for
# most search nodes based on their current max child configuration and other
# parameters. If you wish to take on additional connections, please note
# that you must set your maximum file descriptor limit accordingly (provided
# that the internal setrlimit() call is unable to sufficiently increase your
# current limits). Consult your shell's manual regarding ulimits for more
# details.
#
max_active = -1

###############################################################################
# SEARCH NODE SETTINGS

[search]

#
# Maximum number of "child" nodes you are able to support. If you feel that
# you have adequate processing power and memory, you may increase this value
# until the load is no longer acceptable. Please be sure to read the
# max_active and env_cache settings in this section before you change the
# default value.
#
children = 85

#
# Boolean setting determining whether or not to print token search queries
# through the main logging facility. This can become quite noisy and may
# inflate the size of the log file enormously.
#
noisy = 0

#
# Absolute path where the search database environment should be stored. Make
# sure to provide a path with plenty of hard disk space (~100-300MB) and on a
# device with efficient hard drive access to improve access time when
# swapping cannot be avoided.
#
# NOTE:
# As always, this path is in UNIX format, so Windows users will need to
# hack around this accordingly. If you aren't sure what I mean by this, you
# need to go back and read gift.conf documentation.
#
env_path = ~/.giFT/OpenFT/db

#
# Total cache size for the entire search database environment. The idea here
# is to find a perfect balance between disk access and memory usage, which
# we are still widely experimenting with. If you have a lot of memory to
# dedicate to your search node, by all means increase this value accordingly
# as it will improve overall performance (significantly in some cases).
#
# WARNING:
# Specifications less than 500MB (and we expect you will specify less than
# that) are subject to a 20% inflation due to some libdb implementation
# detail.
#
# NOTE:
# Units are specified in bytes, and as such you will not be allowed to
# specify 1GB or higher. While libdb supports this, the API is more obscure
# than this simple configuration option, hopefully the configuration will
# be extended at some point to support this.
#
env_cache = 31457280

###############################################################################
# LAN MODE FACILITIES

[local]

#
# OpenFT offers a special configuration for users who wish to operate a
# network from within a local area network (LAN). This mode causes giFT to
# reject authorization from any non-local address as well as advertising it's
# presence via the local UDP broadcast. If this switch is non-zero you will
# not be able to contact the main network.
#
lan_mode = 0

#
# When LAN mode is enabled, this configuration switch is used to verify
# which hosts are allowed connection to the core OpenFT port. It is
# highly recommended that you just don't touch this, regardless of what
# lan_mode's value is.
#
# NOTE:
# This switch provides a very crude loophole that could allow you to create
# a "private" OpenFT network between a list of known nodes. Using this
# "feature" is going to be quite cumbersome as it is intended to be used
# by developers only. You have been warned.
#
hosts_allow = LOCAL

bouke · 04-11-2004, 03:39 AM

Quote:

Originally posted by stagnant7
any further ideas....should i just try another frontend ....what one is similar to giftui cos i rekon i like the look of this one....

Try giFToxic. Runs well over here and it looks great!

URL: http://giftoxic.sourceforge.net/

mrcheeks · 04-12-2004, 03:33 AM

the problem is not the gui or the program but your gift setup. You might be using a firewall too just a supposition...

usulix · 09-06-2004, 09:35 AM

I installed giFTd and giFTui (and the protocol plugins) through apt-get install in Debian.

after executing giftd -d

I executed giftui

giftui gave me :

the "giftui : No host to connect /apps/giftui/daemon/host."

I executed giftui -s 127.0.0.1:1213

And it brought the gui right up

seems I had to tell the client what server to connect to.

Hope this might help someone else.

Regards,
G

usulix · 09-09-2004, 05:40 PM

Well...

I was pretty sure that what I had typed worked ...

Or maybe when the connection settings popped up I changed it to the correct setting.

Anyway... further working has me reporting a change:

giftui -s 127.0.0.1 -p 1213

should start the client and let it listen on the default port

Also, there is a patch posted on the giftui website for this situation that might apply.

I am probably going to choose giFToxic, though.

It has almost the same look and seems more stable on my system.

giFTcurs is great too if you don't mind a curses app.