Hello, Thank you for your feedback. To answer to your question, the 'bufReader' attribute was indeed declared 'private' to improve our Local Manager integrity. It shouldn't be an issue since the only two methods that use it (readLine() and releaseResources()) are declared "public" so that you can re...

Hello, Does your Manager extend the class "LogFileManager" or "LocalFileManager"? Since LogMX v3.0.2, you can now extend the default LocalFileManager, and completely replace this LogMX default local file manager with your own manager (go to Tools > Options > Managers). If your Manager doesn't extend...

Hello,

Do you still have this error?

Xavier.

Hello, I personally don't have any idea where the problem is, you should not experience memory issues writing your own Log Manager, since it is not supposed to keep in memory a lot of information. It should only read one line of text from the underlying resource only when it is called ( readLine() )...

Hello, According to the output you give here, it doesn't seem to be the same error (not a GUI column bug but a file parsing bug). Do you get this error with an empty file ? If this is not the case, could you please send us this log file (in Private Message if you prefer). I didn't manage to get this...

Hello isheedm, How about adding: A button in "Options" > "Network" to duplicate a user account (with all its settings) and A dropped-down list on the "Private key" text field so that you can easily select an already selected Private key file (Using a default Private key file seems a bit too specific...

Hello,

LogMX v3.0.2 is now available for download, and fixes this behavior (now all hidden files/folders are shown by default for private key file selection, for Windows/Linux/Mac).

Xavier.

Hello, Thank you for your feedback. Directories starting with "." (like ".ssh") are currently not shown in all LogMX file choosers on Linux, since on Linux, these directories are "hidden directories" (same behavior on Windows but files don't have to start with "." to be hidden). Even if it is possib...

Hello, Thanks for posting here. It is indeed a nominal LogMX behavior here. Using %C{1} in your Log4j configuration file makes it write only the last part of the 'Category' (or 'Emitter'), like 'z' for 'x.y.z'. So your log file should contain 'z' instead of 'x.y.z'. So, if you really use Log4j to wr...

Hello,

LogMX v3.0.1 is now available for download, and contains a fix for this bug.

Xavier.

Hello,

LogMX v3.0.1 is now available for download, and contains a fix for this bug.

Xavier.

Hello, LogMX v3.0.1 is now released, and it finally includes the support of public/private key pair authentication :D. At this time, it supports RSA or DSA OpenSSH private keys (protected or not with a passphrase). To convert your private key using PuTTY, start PuTTY Key Generator, open (or create) ...

Hello, Yes, it's indeed a known bug in v3.0.0 (http://www.logmx.com/forum/viewtopic.php?p=456) which is now fixed in v3.0.1 that will be release in a few weeks. In the meantime, you may want to use the "Recent files" item of "File" menu, or make your config file "config/logmx.properties" in read-onl...

Hello, Here is a simple Log4jPattern for IIS 7.5: %d{yyyy-MM-dd HH:mm:ss} %u{s-IP} %c %m - %u{port} %u{user} %u{c-IP} %u{agent} %p %u{sub-status} %u{w32-status} %u{time-taken} But I suggest you to use a Java Parser Class instead, which is more powerful than Patterns, in order to reformat all these f...

I thought of a possible workaround: you can use the "Recent Files" item of the "File" menu.
LogMX keeps the last 20 opened files, including remote files URL.