On Wed, 14 Feb 2001 13:26:57 -0800, Ben Ocean wrote:
>> > >My point is that httpd.conf could also point to their own home
>> > >directories, or a subdirectory, such as public_html.
>> > >
>> > >This way, the user would have full access to their directories and files.
>> > >
>> > >This is also how I set my web account users up...it also ensures that when
>> > >their accounts are over and done, I can delete them and their sites in one
>> > >fell swoop.
>> >
>> > Please help this novice understand how that's different from what I'm
>> > doing. the httpd.conf points, in the above example, to
>> > /apache/vhosts/myClient
>> > for the account
>> > myClient.com
>> > Isn't this the same thing you're talking about? Also, how do I enable the
>> > client to access his site via ftp? I've chown-ed the myClient folder to
>> his
>> > ownership, same name as his sendmail name: shouldn't it be accessible via
>> > his sendmail password? What am I missing here (obviously something,
>> because
>> > this is what I've done)? Thank you for your help!
>>
>>Nope...subtly different.
>>
>>See, if a user has a home directory, that directory and nearly everything in
>>it is owned by that userid..including the directory. I've never seen anyone
>>have trouble uploading to their homedir, or a subdirectory thereof.
>
>Oy! I'm confused as to the subtle diff. *myClient* appears to be what
>you're calling their homedir. They ftp directly into myClient: that's their
>homedir (if I understand you).
Ok...typically a user's home directory is /home/username. Unless
your /etc/passwd file has /apache/vhosts/<insert directory here>
listed after the username, then that's not their home
directory...it's what youv'e configured apache to see as the Document
Root. Document Root does not necessarily equal home directory.
>>As to ftp access to that directory (other than their homedir), the potential
>>problem is that when you log into their account via ftp, they get dropped,
>>first, to their home directory. If their homedir and the myClient are not
>>the
>>same, then they'll need to "cd" to that directory.
>
>Nope, they're the same. No need to cd.
>
>
>>The problem may be permissions on the /apache/vhosts directory (or the
>>/apache
>>dir)...if the directories above their "myClient" directory are not at least
>>r-x for their user group or others, then they may not even be able to "cd" to
>>their "myClient" directory.
>>
>>What are the file permissions on "/apache" and "/apache/vhosts"?
>
>Don't think this applies, since they would be ftp-ing directly into their
>directory. *apache* is owned by root, *vhosts* by webmaster, and neither
>have any group affiliation.
Of course it could apply. If the parent directories are owned by
root, and not at least r-x for the world, then it's quite possible
that the users won't be able to cd to the parent directories, in the
first place, to get to the web directories you've set up for them.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
