[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    [Fwd: Are we connected ? - Solution-idea more info (2)]
From:       Torsten Rahn <torsten () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-05-15 15:59:57
[Download RAW message or body]


Return-Path: <kde-devel-request@alpha.tat.physik.uni-tuebingen.de>
Received: from ims.rz.uni-kiel.de by saturn.astrophysik.uni-kiel.de (SMI-8.6/SMI-SVR4)
	id QAA26094; Sat, 15 May 1999 16:26:02 +0200
Received: from alpha.tat.physik.uni-tuebingen.de by ims.rz.uni-kiel.de
          with SMTP (PP); Sat, 15 May 1999 16:24:30 +0200
Received: by alpha.tat.physik.uni-tuebingen.de
          id <47705-186> convert rfc822-to-quoted-printable;
          Sat, 15 May 1999 16:11:06 +0200
X-Received: by alpha.tat.physik.uni-tuebingen.de id <47409-21438>; Sat, 15 May
            1999 14:08:45 +0200
X-From_: bj@kiel.netsurf.de Sat May 15 14:08:45 1999
X-Received: from smtp-ham-1.netsurf.de ([194.195.64.97]:2241 "EHLO
            smtp-ham-1.netsurf.de" ident: "NO-IDENT-SERVICE[2]") by
            alpha.tat.physik.uni-tuebingen.de with ESMTP id <47409-21438>;
            Sat, 15 May 1999 14:08:34 +0200
X-Received: from mail-ham-1.netsurf.de ([192.168.10.65]) by
            smtp-ham-1.netsurf.de (Netscape Messaging Server 4.01) with ESMTP
            id FBRWE901.MO2 for <kde-devel@alpha.tat.physik.uni-tuebingen.de>;
            Sat, 15 May 1999 14:08:33 +0200
X-Received: from bj-k6.bogus ([194.64.167.166]) by mail-ham-1.netsurf.de
            (Netscape Messaging Server 4.01) with ESMTP id FBRWE800.CI1; Sat,
            15 May 1999 14:08:32 +0200
X-Received: (from bj@localhost) by bj-k6.bogus (8.9.3/8.9.3) id OAA18701; Sat,
            15 May 1999 14:08:06 +0200
Message-ID: <XFMail.990515140805.Bjoern.Kahl@kiel.netsurf.de>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Old-Return-Receipt-To: Bjoern.Kahl@kiel.netsurf.de
In-Reply-To: <XFMail.990514210030.Bjoern.Kahl@kiel.netsurf.de>
Old-Date: Sat, 15 May 1999 14:08:05 +0200 (CEST)
Organization: Private Linux Site
Sender: bj@kiel.netsurf.de
From: Bjoern Kahl <Bjoern.Kahl@kiel.netsurf.de>
To: kde-devel@alpha.tat.physik.uni-tuebingen.de
Subject: Re: Are we connected ? - Solution-idea more info (2)
Old-X-Envelope-To: kde-devel
Date: Sat, 15 May 1999 14:08:45 +0200
ReSent-Date: Sat, 15 May 1999 16:10:44 +0200 (CEST)
ReSent-From: Martin Konold <konold@alpha.tat.physik.uni-tuebingen.de>
ReSent-To: kde-devel@alpha.tat.physik.uni-tuebingen.de
ReSent-Message-ID: <Pine.LNX.3.96.990515161044.927N@alpha.tat.physik.uni-tuebingen.de>
Old-Return-Path: <konold@alpha.tat.physik.uni-tuebingen.de>
X-Orcpt: rfc822;kde-devel@alpha.tat.physik.uni-tuebingen.de
Reply-To: kde-devel@alpha.tat.physik.uni-tuebingen.de
X-Mailing-List: <kde-devel@alpha.tat.physik.uni-tuebingen.de>
                archive/latest/3313
X-Loop: kde-devel@alpha.tat.physik.uni-tuebingen.de
Precedence: list
Resent-Sender: kde-devel-request@alpha.tat.physik.uni-tuebingen.de
MIME-version: 1.0
Content-transfer-encoding: QUOTED-PRINTABLE
Content-Type: text/plain; charset="iso-8859-1"
X-Mozilla-Status2: 00000000


 Note: This is a resend, first try don't appear at the list after more
       than 14 hour. 

On 14-May-99 Bjoern Kahl wrote:
>  
>   Hallo !
>  
>   I am working some time now on a way to manage Networkconnections to
>   the internet, including a way to query the connection-state.

 Hallo !

 I think, some more info is better.

 It work by having a little daemon running.
 Each Programm "Client" (in my case: shell-scripts) that need
 Networkaccess  register itself (using a small C-Programm) to the daemon,
 the daemon  creates an connection to the Network (using system-provided
 script, on  SuSE-Linux /etc/suseppp/scripts/ppp-up, this is
 configurable) and notify the Client about the link-state.

 Of course, a lot of different Programms can register at the same time.
 The connection is up, as long as one Client is registered.

 (The advantage compared to dial on demand is, the link is only created,
 if there is a Client that want to use to link, not if anything else trys
 to send a packet (like DNS-querys)).

 Clients are separated in two Groups:
 - Request, made by a user-programm
   The Programm register it self, and unregister when done
 - request comming from the system, that is, Programm that are liste in
   a configfile.
   - marked as "system-job" (like Mail or Newstransfer in the early
     morning, or when evver it is cheap to call the net).
   - otherjobs, belonging to a single User
   Such a Request starts, when the daemon starts a Programm listet in
   the configfile, and ends, when the new created process returns.
   I use this kind of Client for Mail and Newstransfer in the morning.


 There is also a GUI-FrontEnd, written in TCL/TK. A User can see in
 this, if the connection is up, and which Programm have registered,
 using his UID. He can cancel all or some of his Networkrequest by a
 mouse-click, or start some predefined Jobs by a Mouseclick (from the
 configfile, I told about in the last paragraph). Also the user can
 see how much time he has used the Network (As I started the work, I
 planed to do a per-user-accounting of Networkusage,  to be able to
 split telephon-costs to the users - I droped that plan  later, but some
 funktion to do some accounting is still there).

 maybe, some thing is usefull for you.



           Bjoern

-- 
+-----------------------------------------------------------------------+
| Björn Kahl ++ Max-Planck-Str.26 ++ 24211 Preetz ++ (ISDN) 04342 76882 |
+-----------------------------------------------------------------------+
 Weitergabe und/oder gewerbliche Nutzung meiner Adresse/TeleNr untersagt.




[prev in list] [next in list] [prev in thread] [next in thread]