From owner-freebsd-elastic@freebsd.org Tue Mar 13 17:06:02 2018 Return-Path: Delivered-To: freebsd-elastic@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD28BF331A1 for ; Tue, 13 Mar 2018 17:06:02 +0000 (UTC) (envelope-from SRS0=bbpu=GD=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C9116980D; Tue, 13 Mar 2018 17:06:02 +0000 (UTC) (envelope-from SRS0=bbpu=GD=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E6C3528417; Tue, 13 Mar 2018 17:58:00 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D621628412; Tue, 13 Mar 2018 17:57:58 +0100 (CET) Subject: Re: logstash improvements To: Mark Felder , freebsd-elastic@freebsd.org References: <1520613071.2637344.1297510176.6EBF62F8@webmail.messagingengine.com> <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Tue, 13 Mar 2018 17:57:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: <1520959523.4160936.1301725184.7519F688@webmail.messagingengine.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-elastic@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Support of ElasticSearch-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 17:06:03 -0000 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 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