Feature Request: Upgrade process improvements

If you think LogMX needs a new useful feature!
isheedm
Posts: 109
Joined: Wed Sep 12, 2007 2:16 pm

Feature Request: Upgrade process improvements

Postby isheedm » Thu Jul 23, 2009 1:55 pm

Here are some ideas that should make the upgrading process easier for me:

1) Have a way for a new LogMX version to import the settings from the previous version (parser definitions, network settings, etc). I prefer that this be done automatically, but a manual method would be good too.

2) Allow the max memory settings (-Xmx option) to be specified in a command line option. I have a Linux machine at work and LogMX is installed by a system admin and is owned by root. I have to copy the logmx.sh file to my home directory and edit it each time I upgrade. If I could simply have a wrapper script that wraps your logmx.sh script and passes in custom memory settings and any other necessary options (-Dconfig.file for example), that would be easier for me.

I just got 1.3.3 installed. Thanks for the good work!

David

isheedm
Posts: 109
Joined: Wed Sep 12, 2007 2:16 pm

Postby isheedm » Thu Jul 23, 2009 2:04 pm

I just found this message which helps me know which files to copy:

http://www.logmx.com/forum/viewtopic.php?t=19

I would still like to have LogMX do the import because I don't want to run into trouble if the config format changes between versions and I blindly copy the logmx.properties file to the new installation (actually, to my home directory on UNIX).

admin
Site Admin
Posts: 417
Joined: Sun Dec 17, 2006 10:30 pm

Postby admin » Mon Jul 27, 2009 9:33 pm

Hello,

As explained in the post you linked, you can safely replace the new config file with your old one, we always make sure that each LogMX version handles older config files (backward compatibility).

You are right, if you can't write in the files located in the LogMX directory (start script + config file), you can copy these files in a directory in which you can write in it. In your ".sh" script, simply use the line:

Code: Select all

CONFIG_FILE_PATH="-Dconfig.file=/mypath/logmx.properties"


Another solution would be to copy/paste the whole LogMX directory (only ~3Mb).

We will try to use any option given to start script as JVM parameters instead of default ones (for v2.0.0 that should be available this fall)

Xavier.

admin
Site Admin
Posts: 417
Joined: Sun Dec 17, 2006 10:30 pm

Re: Feature Request: Upgrade process improvements

Postby admin » Sat Mar 20, 2010 3:35 pm

Hello,

LogMX v2.0.0 is now available, and with its new "logmx.sh" start script, you can now use any JVM options instead of default JVM options included in this start script (these options are to be given through this start script arguments).

Feel free to let me know if you have questions or problems using this new feature.

Xavier


Return to “Submitting a feature request”

Who is online

Users browsing this forum: No registered users and 1 guest