#480 closed defect (wontfix)
Mapfish shutdown
Reported by: | wildintellect | Owned by: | kalxas |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | OSGeoLive | Keywords: | mapfish, 6.0 |
Cc: | live-demo@… |
Description
There's no clear way to shutdown mapfish once you start it, which takes up system resources.
sudo /usr/bin/mapfish stop
Change History (7)
comment:1 by , 15 years ago
comment:2 by , 14 years ago
Keywords: | 4.0 added |
---|
As OSGeoLive is memory constrained, we do want to be able to stop all processes after they have been run. We also are targeting OSGeoLive at non-geeks and hence we don't want to have to stop a process from the command line. Hence, to be consistent with other projects like geoserver and geonetwork, we should have a "stop mapfish" shortcut.
comment:5 by , 12 years ago
Keywords: | 6.0 added; 4.0 removed |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:6 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
I have followed instructions as per [1] and [2] about wsgi application restart. Touching the mapfish wsgi files in apache does not seem to make any difference.
Also "mapfish stop" is not available anymore.
I am closing this since Java applications need far more RAM than this one here.
[1]http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide [2]http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode
comment:7 by , 12 years ago
Cc: | added |
---|
please move the ML email addr from the owner field if you take ownership of a ticket so it doesn't get lost
What do you mean by "clear way to shutdown mapfish"? A shortcut in menu and on desktop?
I was personally in favor of keeping only one MapFish shortcut. I don't think MapFish is using so much system resources, and it's still possible to shutdown MapFish with:
If you think a "Stop MapFish" shortcut is important, then I will update install script to add these shortcuts.