RE: [cobalt-developers] (no subject)

["Kal Amry" <kal@xxxxxxxxxxxxxxx>]

I suggest that you do the following:

chown username filename will do the job

However, if you continue working in the same way, then you'll be having
problems later so I strongly suggests that you straighten up things although
it might take some time; but that all will depend on how far have you gone.

If you have a Raq, then every time you add a site/virtual site, then you
need to make sure that you create a siteadmin user right away, and make sure
when you do work under a particular site, then log in as that particular
site's siteadmin or at least a user of that site. WHY?

Well if you create a site and use the root to work on that site, then that
means the disk quota are not accurate 'cause the root is not counted as part
of that site. Also, there are other reasons thus I suggest that you do this:

1. create a totally new site/virtual site that you will delete later;
however, we will use it so that you follow the same ownership structure of
Cobalt's Default sites.

2. ls -all in that newly created site (/home/sites/site#)

3. Now, open a new window and log in as a site user or siteadmin of the old
site that might need to be restructured.

4. if you see any differences in the third and forth column of (ls -all)
then make sure you adjust the old site structure to match that newly created
site.

5. Log in to that newly created site a siteadmin and ftp some files. Or just
log in and create file.

6. Now, ls -all and look at how the third and forth column are.

The third column I guess is the userNameYouUsedToLogIN and the forth column
is the groupNAME

I forgot how to change the groupOwnership so if you need that, just e-mail
me and I'll look it up for you. Yet I think you won't need it.

7. Go to the old site that we are restructuring, and now see those files
that have ownership or have their third column as something that is not part
of any user in that particular site list.

8. If you see one, then (chown theNameOftheUserforThisOldSite'sFile
filename)

and so on,,,

Let me know if things aren't that clear, but it is really important that you
do some homework first such as navigating the file structure created by
Cobalt so that you start seeing some stuff and things start making some
sense.

Kal Amry

-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx]On Behalf Of Dan
Sent: Thursday, January 11, 2001 5:32 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-developers] (no subject)


Yes, I checked and root does own the file.  Why are files owned by root
restricted despite the rwxr-x-r-x permissions? Who should I chown the file
to for it to be accessible?  Sorry, I'm still new to this.

Also this does not seem to be a problem outside the cgi-bin.  What special
characteristics does a directory named 'cgi-bin' have as opposed to any
other directory (I always thought that 'cgi-bin' was just a naming
convention).

Thank you.

----- Original Message -----
From: "Gerald Waugh" <gerald@xxxxxxxxx>
To: <cobalt-developers@xxxxxxxxxxxxxxx>
Sent: Thursday, January 11, 2001 4:07 PM
Subject: Re: [cobalt-developers] (no subject)


 > "Dan" <dan@xxxxxxxxx> wrote
> > Why is it that whenever I set up a cgi-bin directory and attempt to
browse
> > to it I get a 403 error (Forbidden).    If I try to access any scripts
> > within this directory I either get the same 403 error message (if I
bypass
> > cgiwrap by using AddHandler cgi-script .cgi in the .htaccess file) or a:
> >
> Dan,
> Who owns the script? Sounds like it may be "root".
> prperly chown the file
> And, I use chmod 711.
> Also, is the site setup to run CGI in the GUI?
> Gerald
>
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers

_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers