Hey, You can use a custom storage container to accomplish changing the permissions. Check out the files at sfLuceneDirectoryStorage.class.php and sfLuceneFileStorage.class.php at http://svn.symfony-project.com/plugins/sfLucenePlugin/branches/1.0/lib/addon/Zend/Search/Lucene/ for an example of how to do this.
boopfm523 wrote: > > I did some more investigative work. Below are the two indexes I created > using different users. As mentioned before, neither user can search the > other users index. However, if I switch user to root, the root user is > allowed to read either. Below are the permissions for each. The only > file that differs is the segment file, however that might be b/c of the > index name, I'm not sure. If anybody has some advice on how to make this > work, please let me know. > > [EMAIL PROTECTED] tmp]$ ls -l | grep content_index > drwxr-xr-x 2 apache apache 4096 Dec 13 08:16 content_index > drwxr-xr-x 2 jellin2 users 4096 Dec 13 08:15 content_index2 > [EMAIL PROTECTED] tmp]$ ls -l content_index* > content_index: > total 36 > -rw-rw-rw- 1 apache apache 28547 Dec 13 08:16 _9.cfs > -rw-rw-rw- 1 apache apache 4 Dec 13 08:16 deletable > -rw-rw-rw- 1 apache apache 0 Dec 13 08:16 index.lock > -rw-rw-rw- 1 apache apache 0 Dec 13 08:16 index.optimization.lock > -rw-rw-rw- 1 apache apache 27 Dec 13 08:16 segments > > content_index2: > total 36 > -rw-rw-rw- 1 jellin2 users 28547 Dec 13 08:15 _9.cfs > -rw-rw-rw- 1 jellin2 users 4 Dec 13 08:15 deletable > -rw-rw-rw- 1 jellin2 users 0 Dec 13 08:15 index.lock > -rw-rw-rw- 1 jellin2 users 0 Dec 13 08:15 index.optimization.lock > -rw-rw-rw- 1 jellin2 users 27 Dec 13 08:15 segments > > [EMAIL PROTECTED] tmp]$ diff content_index2/_9.cfs content_index/_9.cfs > [EMAIL PROTECTED] tmp]$ diff content_index/deletable > content_index2/deletable > [EMAIL PROTECTED] tmp]$ diff content_index/segments > content_index2/segments > Binary files content_index/segments and content_index2/segments differ > > > > boopfm523 wrote: >> >> My environment: >> PHP 5.1.6 >> Zend Framework 1.0.3 >> Centos 5 >> Apache 2.2.3 >> >> Permission Issue: >> I'm getting the "Operation not permitted" error when trying to open the >> index directory. I've created the index directory from the command line >> using one user. Then I'm trying to open the index directory using the >> apache user from the web. I get the error message when doing it that >> way. If I access the php script that creates the index directory from >> the web first, then I'm able to open the index fine (the owner is the >> same - apache). I want to create it from crontab once a day, so I don't >> want to access it from the web to create it. The file permissions is >> drwxr-xr-x for the directory and -rw-rw-rw- for the files in the >> directory. When I run it from the command line, the owner is "jellin" >> and group is "users", but when I run it from the web, the user and group >> are both apache. >> >> From what I've read in the documentation, all users should be able to >> read the index, regardless of who created it (by default). This seems to >> be right from the permissions when the directories were created, however >> it doesn't seem to work this way in practice. I even tried to change >> owner and group of the files created from the command line to "apache", >> but I still got the same error message. I can't figure out what the deal >> is, but it seems to be some permission setting within one of the binary >> files that is created. >> >> Last bit of information, right now I'm creating the index directory in >> /tmp for now. >> >> Any help would be appreciated. >> >> > > -- View this message in context: http://www.nabble.com/Lucene-Search-Permission-Issue-tp14262407s16154p14323487.html Sent from the Zend Framework mailing list archive at Nabble.com.
