[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 2003-01-13 at 09:54, Neil Stone wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alex Charrett wrote:
On Mon, 2003-01-13 at 09:44, Neil Stone wrote:
Do the files (passwd access) need to have special perms, uid or gid ? This has been bugging me all weekend and I have finally come to the end of my teather !!
I assume that the account apache is running under is able to access /home/neil/.htpasswd? That'd be the obvious thing....
Alex.
It has been set to several things, nobody.nogroup at some point....
I have now set it to www-data.www-data and still the same !
Debian if that makes a difference ?
You seem to be misunderstanding the question. I'm not asking what the owner of /home/neil/.htpasswd is, I'm asking you if the webserver account can access it. (ie are the directory perms and the file perms granting sufficient access?)
try something like:
# su - nobody -c '/bin/cat /home/neil/.htpasswd'
Where nobody is the username apache runs under.
Alex.
That works... Next ? (now you see the problems i have had ?) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE+Io9PETbMU8Wu6mERAuy9AJ9hZIGGugsg9AyQ3muscvNxvsoRaQCePPAG IuHc5D3ITAg4ENaHRc1UauQ= =80jB -----END PGP SIGNATURE-----
-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.