AnalysisChild persistency handling for unix sockets

[landauermax]

When logs are received from a unix socket, starting from a specific line never makes sense (in fact, it produces unexpected behavior that is difficult to debug and find the cause). To avoid this situation altogether, the AnalysisChild (in particular, the resposioning_data) should (i) not be read/used when the logstream is a unix socket, and (ii) should not be persisted in intervals or when terminating the aminer.

[ernstleierzopf]

Currently there is no issue in the code. In line 450 of the AnalysisChild the UnixSocketLogDataResource is initialized. The repositioning data is never given as a parameter and also the LogStream.UnixSocketLogDataResource does nothing with the repositioning_data parameter.

It is true that repositioning_data is saved, however in the next cycle it is again deleted without being used.

Please reopen if something is wrong with my explanation.

[whotwagner]

I reopened this issue because we do have a very strange behavior when we read from the unix-domain-socket and we have to fix that somehow. I assigned the issue to me because I have to locate the problem first and in order to do this a special testing-environment is needed.