Fixed: file offset still calculated wrong. File was detected as
truncated again :-(
Fixed: loosing the beginning of a partial line
Fixed: A CR is also removed from the EOL

Known issues:
If the last line was logged with CRLF as EOF then the file offset is
not correct calculated (missing one byte for the CR) in the Registry

I found a solution for the issue
https://github.com/elasticsearch/logstash-forwarder/issues/149

gofmt -tabs=false -tabwidth=2

I am not very happy with the formatting gofmt provides, but as there's
the cult of gophers who seems to love this tool, it makes sense to try
to avoid "why not gofmt!?" discussions and not distract existing go
users with differing code style.

Next step is obviously to write logstash-forwarder in !Go just to
avoid formatting wars, right? ;)

Fixed the usage of /etc/default/logstash-forwarder. The previous way did...

Fixed the usage of /etc/default/logstash-forwarder. The previous way did not overwrite the usage of DAEMON_ARGS

This fixes a regression entered during the C -> Go port where the dns
randomizer feature was lost.

file rotation to always be incorrectly detected on linux.

invoke ReplaceFile via Go, so lumberjack's registrar updates will not
be atomic on Windows platform. On windows, the "old" registrar db is
saved as ".lumberjack.old"

  (log/syslog isn't a thing on go in windows)

Update README.md

Fix minor typo

Removed the go subdirectory

Add option to read new files from the top (Useful for testing or backfill)

Fix window size calculation

Added information on generating an ssl certificate

Also added recommendations on where to place the files on disk

seed random