Re: [OSM-dev] Heartbleed

[Simon Poole]

Am 10.04.2014 23:42, schrieb Grant Slater:
.
 The probability is extremely low that any user data was compromised,
 but I would not discourage anyone from changing their password if they
 are concerned.
.

There are some indications (as was to be expected) that the
vulnerability was known well before the public announcement

https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013






signature.asc
Description: OpenPGP digital signature
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Osm2pgsql - expire list incomplete / misses tiles

[Johannes Weskamm]

Hi,

I have a problem with the results of the expire.list, which is generated 
by Osm2pgsql after importing a diff file from OSM.
The list contains not all tiles that need to be expired / refreshed. And 
it may be that it even contains wrong tiles.


The version i use:
Osm2pgsql 0.83.0 (64bit id space)

I use the load-next script to import the diff data. The script itself 
launches the import with the following command:


$OSM2PGSQL --append --slim --cache 1024 --merc --prefix $PREFIX --style 
$STYLE --host $HOST --database $DB --username $USER -e 0-19 -o 
expire.list --verbose $CURRENT 12 2 $PSQLLOG


The imported data is correct and contains all updates that were given by 
the diff file.
The problem is, that the expire list does not contain some of the tiles 
that should be marked as expired, and i have no clue why.


It seems that the regions where updates happend in the database are hit, 
as there are a few expired tiles in the updated regions. But lots of 
tiles which should be expired are missing in the list.


Is there something wrong with the command (could -e 0-19 be a 
problem?), or is this even a bug in osm2pgsql? Does somebody have / had 
similar issues?


Thanks in advance,

J. Weskamm

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev