[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Frontpage, with Webalizer on RAQ4i, solution.
- Subject: [cobalt-users] Frontpage, with Webalizer on RAQ4i, solution.
- From: "Simon Watts" <simon@xxxxxxxxxxx>
- Date: Mon Apr 30 08:25:50 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
OK, sorry if I'm covering covered ground.
I'm still in my first 2 weeks of running a RAQ and already
I've resorted to this list for 3 different problems. 2 of the
3 I found excellent solutions for, but the third hasn't been
quite so easy.
I do a lot of work for clients using the Frontpage extensions,
as I author predominantly in FP2000 it makes sense! BUT after
installing webalizer I ran into a "huge" problem, in that webalizer
carefully loads a folder "stats" into the root directory of any web.
OK, this isn't an issue when ftp is used, but FP doesn't like files
that aren't under it's ownership and so refuses to upload after the
first set of stats have been generated. Great I thought! Anyway I
came and raked through the archives and found a multitude of
solutions, some of which provided a fix, but only short-term until the
next set of stats was run.
As I've gained a little more nerve when telnet'ing in to my RAQ now,
I decided to have a go at the following suggestion to see what the outcome
would be;
> For those with a problem not being able to use FrontPage after installing
> Webalizer;
>
> Telnet in,
> locate webalizer.pl
> edit webalizer.pl by changing httpd to nobody. I did this with;
>
> pico webalizer.pl
> ^w chown (to find the relevant bit in the file!)
> change httpd to nobody
>
> I did this experiment last week on a RaQ3, it seems ok, any advice from
the
> rest of the group?
>
> Joe Quinn joe@xxxxxxxxxx
> QITC Internet Solutions
> Cisco re-seller, Cobalt Sapphire Partner.
> Free Domain Name Registration, Web Site Hosting, Co-location.
> The Best Value Bar None!
> Tel: 44 141 577 6919
> Mobile: 44 776 737 1234
Sure enough it works, but it's only half of the solution. Frontpage still
can't
leave those files alone! Because they don't exist on my local machine it
asks
if I wish to delete them. Whilst this is OK when it's a small site with very
little changing, on a big site there may be stuff that does need deleting,
so
the use of "No to all" is inapropriate.
So I fixed the final hurdle by creating a subweb on my local machine in the
root web called "stats" and just never tell frontpage to "Include Subwebs"
In this way, even though it goes and checks the files out, it never asks
if you want them to be deleted.
My aplogies if this seems too trivial for this user-group, but I felt that
if I was having this problem as a newbie, then the chances were that others
would be too! (Amazingly I rang my tech support number for my dedicated
hosting
providor and the very helpful guy I spoke too had another client with
exactly
the same problem, so even if this info is of no use to anyone here, it has
already been used by one other.
As for the list, at least I know that virtually all the problems I might
face
can easily be resolved by the archives and the fantastic responses of the
users taking part in it
Many thanks
Regards
Si Watts
Owner; SiWIS
http://www.siwis.com