Well, I always chmod 777 when developing on my laptop ;) And I agree it's much easier to get it all working with a sledgehammer _then_ play with getting permissions correct. At least then I know what changed last.....
On Tue, Mar 21, 2017 at 11:51 AM, David Hastings <hastings.recurs...@gmail.com> wrote: > This is true, I was speaking more from a development standpoint as if im > the only one with access to the machine. > > On Tue, Mar 21, 2017 at 2:47 PM, Erick Erickson <erickerick...@gmail.com> > wrote: > >> "Should you be aware of anything". Yes. Your security guys will go >> nuts if you recursively gave 777 permissions. By changing this you've >> opened up your directories to anyone with any access to add any >> program to any directory and execute it. From a security standpoint >> this is very bad practice. >> >> To fix the permissions in a more controlled fashion, you should >> _install_ Solr as the same user who _runs_ solr. That'll straighten >> out your permissions early in the process. Alternatively, add the user >> who installs Solr _and_ the user who Solr runs as in the same Unix >> group and permit the directories to that group. >> >> Best >> Erick >> >> On Tue, Mar 21, 2017 at 11:29 AM, HrDahl <nico_g...@hotmail.com> wrote: >> > When I recursively gave permissions to all folders/files under >> /opt/bitnami >> > it worked! So now I can actually see my core aswell as use it. >> > >> > What when I go into production? Should I be aware of anything? >> > >> > >> > >> > -- >> > View this message in context: http://lucene.472066.n3. >> nabble.com/Error-creating-core-da-Error-opening-new- >> searcher-tp4326041p4326085.html >> > Sent from the Solr - User mailing list archive at Nabble.com. >>
