-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osrm-datastore --springclean: .hsgr file must be specified #1360
Comments
Probably a minor regression in the command line parsing code. Will look into it later today. |
Cant' reproduce. The |
Also, make sure to use |
The error appears to be produced here: Are you saying that
It doesn't feel right to me that the code to cleanup the shared memory is hidden away in an optional tool. Surely it makes more sense as an option to osrm-datastore? The first place I looked for this functionality was Thanks. |
I can reproduce the above with latest master.
|
@faheemmughal you need to use |
I will try that. Thanks @TheMarex |
BUILD_TOOLS did give me access to springclean utility, however it added a lot of other dependencies (read sub dependencies of I will agree with @SystemParadox on this that it shouldn't be an optional tool when shared_memory is something we ought to be using in production to ensure cleaning after service is shutdown. |
The GDAL dependency comes from the components tool only. There is already an issue about how to transition away from GDAL to GDAL 2 or something like GeoJSON that would eliminate the dependency completely: #1738 |
Hi. I'm just starting out with osrm, trying to understand how shared memory works.
The springclean option (#947) does not appear to work:
According to
ipcs
, the shared memory does not get released.If I specify the file as well as springclean, it seems that the springclean option has no effect. It does exactly the same as without the springclean option - the data remains in the shared memory. The key reported by
ipcs
changes, so I would assume that this reloads/replaces new data as described in the docs.Is this a bug with
springclean
or am I misunderstanding something?Thanks.
The text was updated successfully, but these errors were encountered: