[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Removing the ~ (tilde) Slightly OT Frontpage publish with owned files
- Subject: Re: [cobalt-users] Removing the ~ (tilde) Slightly OT Frontpage publish with owned files
- From: "Chris Calabrese" <webmaster@xxxxxxxxxxxxxxx>
- Date: Sun Aug 12 19:30:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
----- Original Message -----
From: "Simon Watts" <simon@xxxxxxxxxxx>
> > If you try to publish with FrontPage (to a RaQ 4 at least)
> > and any of the
> > files existing in the web directory you're publishing to
> > are set as owned by
> > anything but "nobody," FrontPage will generate an error
> > saying something
> > like "Can't set permissions on xyz" and refuse to publish.
> > There are ways
> > around that, but I don't want to create a big problem to
> > solve a small one.
> >
>
> Sorry to disagree, but for the sake of the archives;
>
> On a RaQ4, using Frontpage to publish, you can overcome the "Can't set
> permissions on xyz" problems very very easily.
> Simply set up, on your local hard drive copy of your web, any folder
> which you don't want Frontpage to publish to as a FP subweb.
> All that needs to be done then is to ensure that any htm, html, gif or
> jpg files are owned by "nobody". Frontpage doesn't bother looking at
> anything other than the html files in your subweb directories, so cgi,
> pl etc files can all have their correct permissions and ownerships
> without FP spitting its dummy out.
>
> I use this method extensively for cgi-bins and the files they need to
> contain. I create a subweb locally in FP, place the relevant files and
> edit them into the correct structure locally, then create my cgi-bin
> folder via ftp, and upload the contents also via ftp.
> I then SSH in and change permissions on any htm files back to nobody,
> then finally publish the rest of the web via FP, ensuring that in the
> Publish settings that the tick box is not selected for Publish
> Subwebs" et voila, my cgi's
That's "very very easy" for you and me, but it's not very very easy for the
FrontPage users on the server who don't have root access to change
permissions. (Try reciting that last paragraph to your average FrontPage
user and see if they think it's "very very easy.") Add to the equation the
fact that I was talking about Webalizer (not CGI scripts), which creates a
new set of .html files each month in every stats directory, and things get
more complicated.
You don't need to disagree with me; as I said in my previous e-mail, there
are ways around the FrontPage permissions problem but they create a bigger
problem than the original problem I was trying to fix.
~ Chris Calabrese