Hello,
You could try to do the inverse. Put the apache user in the group of
user1, that you use to make the upgrades. Set the owner of the files to
user1 and allow then be edited by group (g+w). So the apache user can
read and execute the files.
If you use any king of upload function, or any other thing that makes
apache to write files, add group write permission to the directory where
appache will write.
Other solution is to write a script that executes every 1|5|15|30 min
(your choice) via crontab, that perform a chown in the directory you
want to change ownership.
[]s
ESGLinux escreveu:
Hi all for your answers,
I´m going to tell you why I´m trying to do that. it´s more complicated that
the use of chmod, but it is the begining ot the problem,
I have a webserver with the user apache being the owner of all under
/opt/www/.
Well, this user hasn´t a shell (it´s is /sbin/nologin) so I can´t connect
with this user.
So I use another user that makes the upgrades of my application and web
pages, (I use rsync to make this upgrades). The problem is that with this
user I can´t change the permission to the files.
One more thing, when I update one file, it changes the owner and group of
the file to the user that I use to connect.
I use this:
rsync -azv -e 'ssh ' --delete /locatpatch/* user2@server:/opt/www/
perhaps it´s a problem with what I want to do (I know, that I can dive shell
access to the apache user and do all with it, but I prefer not to grant that
permissions to this user)
any idea?
ESG
2010/1/14 <m.roth@xxxxxxxxx>
--
Fábio da Silva Júnior - fjuniorlista@xxxxxxxxx
----- http://fabioojunior.wordpress.com -----
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
