scripts don't work cleanly on FreeBSD
-------------------------------------
Key: SOLR-93
URL: http://issues.apache.org/jira/browse/SOLR-93
Project: Solr
Issue Type: Bug
Components: replication
Affects Versions: 1.1.0
Reporter: Hoss Man
As first reported by liuping.james in this thread...
http://www.nabble.com/SolrDistribution-is-tested-by-FreeBSD--tf2869098.html#a8019145
...the various distribution scripts have issues using the FreeBSD version of
bash ... more specificly, they don't run cleanly via "bash script-name" on
FreeBSD systems.
notes from when i verified this...
--------------------------------------------------
I just tried this out on the only FreeBSD system i have access to
(minotaur.apache.org) and found a few things...
1) /bin/bash doesn't exist
2) /bin/sh is true sh, not bash
3) bash is installed in /usr/local/bin/bash
...i'm not sure how standard these are among FreeBSD systems.
I also verified that rsyncd-enable and rsyncd-disable do work if you run
them explicitly through bash, but for some reason you must use the -u
option, and even then it logs a straing warning about scripts.conf...
[EMAIL PROTECTED] bash solr/bin/rsyncd-enable -h
/home/hossman/tmp/apache-solr-1.1.0-incubating/example/solr/conf/scripts.conf:
l: command not found
solr/bin/rsyncd-enable: illegal option -- h
usage: rsyncd-enable [-u username] [-v]
-u specify user to sudo to before running script
-v increase verbosity
-V output debugging info
[EMAIL PROTECTED] ls solr/logs/
[EMAIL PROTECTED] bash solr/bin/rsyncd-enable
/home/hossman/tmp/apache-solr-1.1.0-incubating/example/solr/conf/scripts.conf:
l: command not found
!udo: no passwd entry for
[EMAIL PROTECTED] ls solr/logs/
[EMAIL PROTECTED] bash solr/bin/rsyncd-enable -u hossman
/home/hossman/tmp/apache-solr-1.1.0-incubating/example/solr/conf/scripts.conf:
l: command not found
[EMAIL PROTECTED] ls solr/logs/
rsyncd-enabled rsyncd.log
...so above and beyond the sh vs bash and patch issues .. there does seem
to be a compatibility issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
