Date: Tue, 13 Mar 2018 17:57:58 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Mark Felder <feld@FreeBSD.org>, freebsd-elastic@freebsd.org Subject: Re: logstash improvements Message-ID: <fb721ff5-a216-94cd-db66-2c812bac5a96@quip.cz> In-Reply-To: <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> References: <1520613071.2637344.1297510176.6EBF62F8@webmail.messagingengine.com> <op.zfmevbs0pvh08s@laptopidis> <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Felder wrote on 2018/03/13 17:45: > > > On Fri, Mar 9, 2018, at 12:58, Fotis Zabaras via freebsd-elastic wrote: >> On Fri, 09 Mar 2018 18:31:11 +0200, Mark Felder <feld@freebsd.org> wrote: >> >>> As logstash6 has fewer users at the moment, I've started making large >>> improvements to the port. My recent commit does the following: >>> >>> sysutils/logstash6: Many improvements >>> >>> - all config files are now in ETCDIR >>> - rc script is updated to use logsearch.yml to locate logging config >>> (logstash.conf) >>> This will not break existing setups that used the >>> ETCDIR/logstash.conf file, >>> as that is >>> now part of the default logstash.yml file >>> - added configtest to rc script >>> - sample logstash.conf file no longer includes invalid syntax >>> - pkg-message had historical messages removed >>> >>> >>> >>> Previously all of the logstash.yml, jvm.options, etc were in >>> /usr/local/logstash/config which is not an ideal location and may not be >>> preserved between pkg upgrades. Now it's in ETCDIR where it belongs. >>> >>> Soon I plan to also add a dedicated daemon user instead of running as >>> root by default. There's no good reason for this unless you need to >>> listen on syslog port 514, but there are other ways of solving that >>> problem (MAC framework, for example). >>> >> >> Nice :) >> Should we add also on the pkg-message the requirement of /proc to be >> mounted >> as it is needed by java? >> > > I tend to automatically mount procfs and fdescfs for Java programs, but this would be a useful message for new users. I have seen this message printed by some Java ports in the past but I never mounted procfs and fdescfs. What problems can I expect? Will the application print some warnings? For example I am running Elasticsearch on 5 machines without procfs and fdescfs. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fb721ff5-a216-94cd-db66-2c812bac5a96>