[jira] Created: (SOLR-93) scripts don't work cleanly on FreeBSD

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
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...

hossman@minotaur$ 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

hossman@minotaur$ ls solr/logs/
hossman@minotaur$ 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
hossman@minotaur$ ls solr/logs/
hossman@minotaur$ 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
hossman@minotaur$ 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465539 ]

Bertrand Delacretaz commented on SOLR-93:
-----------------------------------------

I tried that on minotaur as well...and it works for me (apart from the bash location issue), even without -u:

[bdelacretaz@minotaur ~/solr]$ ls solr/logs
[bdelacretaz@minotaur ~/solr]$ bash solr/bin/rsyncd-enable
[bdelacretaz@minotaur ~/solr]$ ls solr/logs/
rsyncd-enabled  rsyncd.log
[bdelacretaz@minotaur ~/solr]$ rm solr/logs/*
[bdelacretaz@minotaur ~/solr]$ bash solr/bin/rsyncd-enable -u bdelacretaz
[bdelacretaz@minotaur ~/solr]$ ls solr/logs/
rsyncd-enabled  rsyncd.log
[bdelacretaz@minotaur ~/solr]$

I used the current scripts from SVN, (rev 497147) copied from trunk/example/solr/bin.

Minotaur is running FreeBSD 6.1-RELEASE-p10 (SMP).

Dunno what has changed since you ran your tests?

Minotaur's has been up for 21 days, so it's not been updated since you ran them.




> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469732 ]

J├╝rgen Hermann commented on SOLR-93:
------------------------------------

If this is your only problem:

/home/hossman/tmp/apache-solr-1.1.0-incubating/example/solr/conf/scripts.conf: l: command not found
!udo: no passwd entry for

that is easily fixed, since it's caused by CRs in the distributed scripts.conf file.

> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607381#action_12607381 ]

Richard "Trey" Hyde commented on SOLR-93:
-----------------------------------------

snapshooter will also fail on FreeBSD systems.   In the 1.3 dailys (big improvement from 1.2) there is a big if block that needs to change

{code}
if [[ "${OS}" == "SunOS" || "${OS}" == "Darwin" ]]
then
  orig_dir=$(pwd)
  mkdir ${temp}
  cd ${data_dir}/index
  find . -print|cpio -pdlmu ${temp} 1>/dev/null 2>&1
  cd ${orig_dir}
else
  cp -lr ${data_dir}/index ${temp}
fi
{code}

Need to add a || "${OS}" == "FreeBSD" .. and NetBSD .. OpenBSD... *BSD   The  find/cpio snippet appears to work as expected.

I wonder if the cases should be flipped though.  I think most *NIX systems DON'T use GNU cp (and thus lack the -l option).

> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621039#action_12621039 ]

Otis Gospodnetic commented on SOLR-93:
--------------------------------------

Richard, SOLR-682 is now fixed.  Does it take care of this particular problem, too?
Should we close this one?


> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621065#action_12621065 ]

Richard "Trey" Hyde commented on SOLR-93:
-----------------------------------------

I don't use all the scripts but I believe all the problems I have encountered are now resolved (except the crappy Java support and bash in the wrong place but that is not a solr issue).   I would close and see if anyone speaks up.

> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Otis Gospodnetic resolved SOLR-93.
----------------------------------

    Resolution: Fixed
      Assignee: Otis Gospodnetic

OK, closing.  If you encounter other OS-related problems, feel free to submit a patch.  Of course, SOLR-561 is coming in Solr 1.4! :)


> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://issues.apache.org/jira/browse/SOLR-93
>             Project: Solr
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 1.1.0
>            Reporter: Hoss Man
>            Assignee: Otis Gospodnetic
>
> 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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-93) scripts don't work cleanly on FreeBSD

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716636#action_12716636 ]

Nick B commented on SOLR-93:
----------------------------

The snapinstaller script explicitly calls the 'commit' script, hence you can't prefix the command with 'bash' as above.

I think the correct solution is to just use /usr/bin/env - that way it will work on linux and bsd amongst other platforms.

-#!/bin/bash
+#!/usr/bin/env bash

Nick




> scripts don't work cleanly on FreeBSD
> -------------------------------------
>
>                 Key: SOLR-93
>                 URL: https://issues.apache.org/jira/browse/SOLR-93
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (scripts)
>    Affects Versions: 1.1.0
>            Reporter: Hoss Man
>            Assignee: Otis Gospodnetic
>
> 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...
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ ls solr/logs/
> hossman@minotaur$ 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
> hossman@minotaur$ 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.
-
You can reply to this email to add a comment to the issue online.