[
https://issues.apache.org/jira/browse/SOLR-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905448#comment-17905448
]
Eric Pugh commented on SOLR-17594:
----------------------------------
[~mfechner] thanks for this.
Are you familiar with the
{color:#000000}org.apache.solr.cli.SolrProcessManager class that was recently
added to the CLI? It is currently used by the StatusTool to check if Solr is
running, and it lets you understand what ports and pids are being used.
{color}
We are currently trying to remove the amount of scripting code in bin/solr (and
bin/solr.cmd) in favour of more Java based code, as that is easier for us to
test and maintain.
Would you be interested in collaborating on ripping out the use of lsof
completely in favour of Java code? I haven't dug into it, but I could
imagine that we could use eitehr the StatusTool directly, or maybe add a new
Java based Tool to replace what we are doing with lsof. That would then cover
the sockstat use case as well. It might let us restore our cygwin support as
well ;)
> Allow usage of sockstat to detect if solr could be started successfully
> -----------------------------------------------------------------------
>
> Key: SOLR-17594
> URL: https://issues.apache.org/jira/browse/SOLR-17594
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Matthias Fechner
> Priority: Major
>
> The current solr bash script is using lsof to detect if solr was started
> successfully.
> The lsof binary does not exist on FreeBSD, but sockstat is used.
> The linked PR from github adds the possibility to use sockstat if available.
>
> I will also make the change available on FreeBSD.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
