Am 08. Apr, 2002 schwätzte Charlie Bullen so:

> drwxr-xr-x  14 webuser  webuser      4096 Mar  8 15:43 .
> drwxr-xr-x  23 root     root         4096 Mar 12 07:18 ..
> drwxr-xr-x   2 webuser  root         4096 Dec 14 09:43 ancientlostcities
> drwxr-xr-x  13 webuser  root         4096 Dec 19 16:26 artitour
> drwxr-xr-x   2 root     root         4096 Mar 29  2001 cgi-bin
> drwxr-xr-x   2 webuser  root         4096 Dec 14 09:44 eleganttrains
> drwxr-xr-x   2 webuser  root         4096 Dec 14 09:44 famoustrains
> drwxr-xr-x   3 root     root         4096 Dec  1 08:18 html
> drwxr-xr-x   3 root     root         4096 Dec  1 08:18 icons
> drwxr-xr-x   2 webuser  root         4096 Dec 14 09:44 incense
> drwxr-xr-x  10 webuser  root         4096 Dec 19 16:22 musitours
> drwxr-xr-x  10 webuser  root         4096 Mar 10 10:09 qe2
> drwxr-xr-x  10 webuser  root         4096 Mar 10 10:11 qm2
> drwxr-xr-x   7 webuser  webuser      4096 Apr  7 14:42 travelcruise
>
> Taking /travelcruise as an example, I can ftp files to the directories,
> but if I want to upload a modified file, I can not over write the existing
> file loging in as webuser. If I go to the command line and change to
> root,I can remove the old file and then upload the revision loged in as
> webuser.

The perms on *that* dir are fine. What are the perms on the file? Being able to
add new files lets you know that your dir perms are OK. Not being able tothe
overwrite a file indicates that it's a perms prob with that particular file.
Who owns the files after they're created? Why? You either want webuser to
own them or to have the group be webuser and make sure webuser logs in with
group of webuser and that the files get created with write perms for the
group.

ciao,

der.hans
-- 
#  This line intentionally left blank.
# "The purpose of IT is to seamlessly and transparently provide the other
# 9/10's of the [iceberg] for people who need to work with chunks
# of floating ice." -- Strata Rose Chalup