Things have changed reasonably for the 5.0 release. In case of a standalone mode, it still defaults to the server directory. So you'd find your logs in server/logs. In case of solrcloud mode e.g. if you ran
bin/solr -e cloud -noprompt this would default to stuff being copied into example directory (leaving server directory untouched) and everything would run from there. You will also have the option of just creating a new SOLR home and using that instead. See the following: https://cwiki.apache.org/confluence/display/solr/Getting+Started+with+SolrCloud The link above is for the upcoming Solr 5.0 and is still work in progress but should give you more information. Hope that helps. On Tue, Jan 6, 2015 at 1:29 AM, Dominique Bejean <dominique.bej...@eolya.fr> wrote: > Hi, > > In release 4.10.3, the following lines were removed from solr starting > script (bin/solr) > > # TODO: see SOLR-3619, need to support server or example > # depending on the version of Solr > if [ -e "$SOLR_TIP/server/start.jar" ]; then > DEFAULT_SERVER_DIR=$SOLR_TIP/server > else > DEFAULT_SERVER_DIR=$SOLR_TIP/example > fi > > However, the usage message always say > > " -d <dir> Specify the Solr server directory; defaults to server" > > > Either the usage have to be fixed or the removed lines put back to the > script. > > Personally, I like the default to server directory. > > My installation process in order to have a clean empty solr instance is to > copy examples into server and remove directories like example-DIH, > example-shemaless, multicore and solr/collection1 > > Solr server (or node) can be started without the -d parameter. > > If this makes sense, a Jira issue could be open. > > Dominique > http://www.eolya.fr/ > -- Anshum Gupta http://about.me/anshumgupta
