gtk-gnutella logo
現在のバージョン: 1.2.3

Unix のためのグラフィカルな Gnutella クライアント

gtk-gnutella は Gnutella 用のサーバントです。 GTK+ (1.2 またはそれ以上) および libxml をサポートする全ての Unix, それに類似するシステム上で動作します。GNOME デスクトップ環境は必要ありません。 現在 Linux (Debian 2.2) で開発・テストされていて、少なくとも Linux, FreeBSD, NetBSD, Darwin, Solaris, Tru64 UNIX (OSF/1), SGI IRIX, BeOS 上で動作することが確認されています。 CPU アーキテクチャには x86, AMD64, PowerPC, SPARC, MIPS が含まれます。

gtk-gnutella は GNU 一般公衆利用許諾契約書 (GPL) の条件下でリリースされています。

gtk-gnutella はまだ完全ではありませんが、十分機能的なものになっています: 共有、検索およびダウンロードが可能です。また安定していますので、利用者は数日間そのままにしておけます。

アイデアや感想等がありましたら gtk-gnutella-devel メーリングリストまでお寄せ下さい。 バグは SourceForge.net の バグ追跡システム に報告して下さい。

C での開発や文書作成で手伝って下さる方を随時募集しています

ニュース

3 March 2024, Version 1.2.3 Released

This is a maintenance release with minor bug fixes.

Improvements
Bug Fixes
Under the Hood

25 February 2022, Version 1.2.2 Released

This is a maintenance release with major bug fixes.

There were several shortcomings with bandwidth management: capping was not performed correctly and could overuse uploading bandwidth. Also when the DHT is turned off or on, we need to recompute proper bandwidth stealing.

Corruption of the DHT disk databases could also lead to a crash.

There was a critical old bug in the Dynamic Querying layer that affected Ultrapeers mostly: we could corrupt memory and/or crash when the current node was removed and we were processing a Dynamic Query for that node. This is more likely to happen when running as an Ultrapeer but it could also affect nodes running as leaves, although the probability of that bug happening is much less in that case.

Finally, it is best to not iterate on a global list that could get changed due to a node removal. This was the case when sending pongs to neighbouring nodes, so we now take a private copy.

Improvements
Bug Fixes
Under the Hood

12 July 2021, Version 1.2.1 Released

This is a maintenance release with minor bug fixes.

Note that our project IRC #gtk-gnutella channel is now on irc.libera.chat.

When launching gtk-gnutella and there is a stale lockfile present, listing some PID, and it happens that there is already another process running under this PID, we abort, complaining that another gtk-gnutella is running. However, if the lockfile is really stale, and the PID listed in there has nothing to do with gtk-gnutella at the moment, the user will need to remove the stale lockfile. Hence we show them the command to run, listing the full lockfile path so that it is easy to overcome this little inconvenience!

When using hashtables for memory management, it was possible to trigger a resizing and, during the course of operations, have further memory used, requiring tracking of new items in the same hashtable we were in the process of resizing. That led to double VMM freeing of the region used to store the data.

Add properties to track bytes exchanged by schedulers. These properties track the amount of bytes exchanged by session and are reset to 0 whenever a new user session starts. It allows users to see the actual amount of data consumed by running gtk-gnutella sessions, programatically via the shell interface.

Add -t switch to shell "status" command: this displays the total amount of bandwidth consumed during the session for the different schedulers.

Improvements
Bug Fixes
Under the Hood

古いニュース...

Users Love Us Community Choice SF Favourite Community Leader Open Source Excellence SourceForge.net Logo RSS Feed Available Open Hub metrics Coverity Scan Build Status gtk-gnutella at GitHub
Copyright © 2000-2014 Yann Grossel, Raphaël Manfredi および手伝って 下さった数多く の方々。