I don't think it's 1 or 2. I have SELinux disabled and both web/conf/* and solr/biblio/conf/* are owned root.

It's likely 3. Which make sense. I caused havoc once editing a solr conf file without first stopping vufind/solr. When it's free, I'll test this on the development server.

Thanks, Demian!

On Wed, Feb 6, 2013 at 3:53 PM, Demian Katz <demian.katz@villanova.edu> wrote:

I just tried this on my test server and I had no problem saving a Solr configuration with 777 permissions…  but a few thoughts:


1.)    Is it an SELinux issue?  You need to set modes in order to allow Apache to write files when SELinux is enabled.

2.)    Is it an ownership issue?  Does changing the file ownership to apache help?

3.)    Is it a locking issue?  Does it make a difference if Solr is running or not running?


- Demian


From: Nathan Tallman [mailto:ntallman@gmail.com]
Sent: Wednesday, February 06, 2013 2:56 PM
To: vufind-tech
Subject: Re: [VuFind-Tech] Admin Module


I just noticed that web/conf files have "-rwxrwxrwx." for permissions while solr/biblio/conf files have "-rwxrwxrwx" -- I'm not sure what the trailing period means, but maybe it's part of the problem?




On Wed, Feb 6, 2013 at 2:45 PM, Nathan Tallman <ntallman@gmail.com> wrote:

I'm enabling (and locking down) the admin module, so some of the basic settings can be changed by other staff members, in a pinch.


The only problem I'm having is getting the solr conf files to save changes. They have 777 permissions, the same as web/conf--which does work.


Any ideas?