-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why .deb rather than source? #10
Comments
Unfortunately, yes. @mrdavidlaing inquired about the missing 2.9 source tarball and the More recently, logstash (and so logsearch) dropped SSLv3 in favor of TLS. For the short term, we decided to use the DEB so we could continue and For the long term, it'd be nice to just switch to using rsyslog which is In the meantime, open to other ideas, too. On Friday, November 20, 2015, Dr Nic Williams [email protected]
Danny Berger |
FWIW, I think we should give up on NXLog; and switch to using the embedded rsyslog like most other bosh releases |
If it's helpful I made a little simple-remote-syslog-boshrelease after I looked at this repo and nxlog boshrelease. I borrowed all of it from other releases; but perhaps it's a useful starting point for you? On Thu, Nov 26, 2015 at 7:01 AM, David Laing [email protected]
|
@drnic - found it - thanks! https://github.com/cloudfoundry-community/simple-remote-syslog-boshrelease Out of interest, what are you using to forward logs to syslog? |
By using the .deb the bosh release can only be used on Debian stemcells - source/nxlog-ce_2.9.1347_ubuntu_1404_amd64.deb
https://nxlog.org/products/nxlog-community-edition/download includes "Source code" option (albeit the version is older; wtf?)
The text was updated successfully, but these errors were encountered: