[email protected]
[Top] [All Lists]

Bug#329018: marked as forwarded (azureus: please don't hard-code startSo

Subject: Bug#329018: marked as forwarded azureus: please don't hard-code startSocket port
From: Debian Bug Tracking System
Date: Sun, 18 Sep 2005 20:18:03 -0700
Your message dated Sun, 18 Sep 2005 21:03:12 -0600
with message-id <[email protected]>
has caused the Debian Bug report #329018,
regarding azureus: please don't hard-code startSocket port
to be marked as having been forwarded to the upstream software
author(s) Azureus Team <[email protected]>.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at 329018-forwarded) by bugs.debian.org; 19 Sep 2005 03:03:44 +0000
>From [email protected] Sun Sep 18 20:03:44 2005
Return-path: <[email protected]>
Received: from qproxy.gmail.com [] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EHBwW-0006PO-00; Sun, 18 Sep 2005 20:03:44 -0700
Received: by qproxy.gmail.com with SMTP id o12so82465qba
        for <[email protected]>; Sun, 18 Sep 2005 20:03:12 -0700 
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
Received: by with SMTP id h14mr34115qbg;
        Sun, 18 Sep 2005 20:03:12 -0700 (PDT)
Received: by with HTTP; Sun, 18 Sep 2005 20:03:12 -0700 (PDT)
Message-ID: <[email protected]>
Date: Sun, 18 Sep 2005 21:03:12 -0600
From: Shaun Jackman <[email protected]>
Reply-To: Shaun Jackman <[email protected]>
To: Azureus Team <[email protected]>
Subject: Bug#329018: azureus: please don't hard-code startSocket port
Cc: [email protected]
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <[email protected]>
Delivered-To: [email protected]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

---------- Forwarded message ----------
From: Henrik Johansson <[email protected]>

On multi-user operating systems, it would make sense to run one azureus
instance/user. The current implementation, which always checks port 6880 fo=
a running instance, only allows one instance/machine. (Unless
-DMULTI_INSTANCE=3Dtrue is given, in which case a new instance is started e=

Current behavior:
If I am running azureus on my uid, and my roommate (who is logged in
on the same computer) tries to start one, azureus tries to feed his
arguments to my instance instead. (I'm not sure if it works, but it's
not what I want anyway.)

Wanted behavior:
If no azureus instance is running with the users uid, an instance is
started. If an instance already exists with the users uid, args are
passed to it.

Proposed solution 1 (quick):
Add a setting for which port to check and use for the StartSocket.

Proposed solution 2 (good, but perhaps platform dependent):
Check ports within some (hard coded) range for a running instance with
the same uid as the starting instance. Start a new instance if none is

To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

<Prev in Thread] Current Thread [Next in Thread>
  • Bug#329018: marked as forwarded (azureus: please don't hard-code startSocket port), Debian Bug Tracking System <=