Hi, Bruce,
Markus Schaber wrote:
>>>It does not find as much liers as the script above, but it is less
>>Why does it find fewer liers?
>
> It won't find liers that have a small "lie-queue-length" so their
> internal buffers get full so they have to bloc
), but not
syncs/write rate.
Both of them can be captured by the other script, but not by my tool.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatent
SB/FireWire to IDE case, and an older linux cryptoloop implementations,
IIRC).
If you're interested, I can dig for the C source...
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software
t application into a
multi-deployment application with some limited cooperation / data sharing.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.noso
nd such shield the application
from directly accessing the global data. We even need to mere local and
global data this way in some cases.
It is ugly, but it works fine and is manageable.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Devel
view
before reCREATEing it, maybe it's best to encapsulate this inside a
transaction or use a scheduled downtime.
Btw, it seems that your '.'-key is broken and chatters. :-)
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software D
estore procedure should following the lines of:
- create new database
- install postgis into database, including spatial_ref_sys.sql
- install the schema dump via postgis_restore.pl
- install the geometry_columns dump (and manually drop the obsolete
columns afterwards).
- install all other dumps via
