Xref: utzoo comp.protocols.iso:1577 comp.protocols.misc:1214 alt.sys.sun:2831
Path: utzoo!utgpu!cs.utexas.edu!uunet!snorkelwacker.mit.edu!ira.uka.de!fauern!faui43.informatik.uni-erlangen.de!eckert
From: eckert@immd4.informatik.uni-erlangen.de (Toerless Eckert)
Newsgroups: comp.protocols.iso,comp.protocols.misc,alt.sys.sun
Subject: Re: X.25 accounting on Suns
Message-ID: <1991Feb26.170211.2205@informatik.uni-erlangen.de>
Date: 26 Feb 91 17:02:11 GMT
References: <1991Feb25.033130.21139@mel.dit.csiro.au>
Organization: CSD., University of Erlangen, Germany
Lines: 26

From article <1991Feb25.033130.21139@mel.dit.csiro.au>, by smart@manta.mel.dit.csiro.au (Robert Smart):
> How do you do x.25 accounting fo Sunlink X.25? We want to keep track
> of who we are connecting to and how many packets we are sending.
> 
> The only idea we have come up with to achieve this is to connect
> to the x25 trace port. There has to be an easier way.

If it's only for incoming/outgoing x28/x29 connections, these are logged 
in /usr/adm/x29serverlog and /usr/tmp/x29userlog. Otherwise there is
not much of a chance than actually to use the trace socket or
rely on external information (good X.25 switches can do this job
four you though they can't find out about the user initiating the
job).
If you have Sunlink X.25  6.0 or older then it does'nt make much
sense to use the trace socket, because it is exclusive access,
so you won't be able to use x25trace while you're program is running
(or the other way round).

Vcstat, as far as i know does not use the trace socket, but the
management socket, which (as far as i remember) can only be used
by polling, so you may end up getting inaccurate numbers.
---

             Toerless.Eckert@informatik.uni-erlangen.de
    /C=de/A=dbp/P=uni-erlangen/OU=informatik/S=Eckert/G=Toerless
  No signature due to pending copyright lawsuit over last signature


Brought to you by Super Global Mega Corp .com