Install/compile on Free BSD 11

I'm trying to install/compile the Community Edition on FreeBSD 11. I'm having the same issues as were addressed in here: https://nxlog.co/question/2570/freebsd-port

ie "The port currently needs a little bit more work since it does not properly pick up PCRE from when not in /usr (as on FreeBSD) and I don't really like to hack use to work around that ;-)."

AskedDecember 21, 2018 - 10:51pm

No TCP Keep-Alive?

We are facing these error messages in NXLog log files:

AskedDecember 14, 2018 - 12:54pm

NXlog crashes on service start


We have had few instances on several servers in the past few weeks, where the NXlog application crashes when starting the service. Commonality so far is Windows Server 2012 Standard. Reinstall of the application corrects the problem, but doesn't sound like a solution. Anyone else experiencing this issue? Any fixes?

Following is the error from the Application Log:

AskedDecember 10, 2018 - 11:36pm

Latest nxlog-ce formally supports Windows Server 2016 ? / solved 256 sources limitation?

I have two questions.

First, a latest nxlog-ce formally supports Windows Server 2016 ?
I saw the following url, and now it seems to support the Windows Server 2016.


Second, the eventlog source limitation on Windows Server 2016 (the OS have over 256 sources, but the nxlog could treat up to 256 sources) is solved ?
I saw the following forum questions.

AskedDecember 10, 2018 - 3:31am

Have NXLog always forward file on disk (even if it hasn't changed)

I have the following NXLog config below that reads a file from disk and forwards it to another host (syslog). By default, it appears NXLog only forwards the data in the log file if it has changed.

How can you configure 'nxlog.conf' so that it always forwards the file, even if the data hasn't changed?

<Input in>
Module im_file
File "C:\\myfile.txt"

AskedDecember 7, 2018 - 5:14pm