Re: [cobalt-users] Webalizer .pkg for the Raq3

["Support" <cobalt-lists@xxxxxxxxxxxxx>]

I have to ask(sorry)

Someone posting info on how to get a RaQ3 to do lookups for webalizer. Could
someone either forwarded that to me  or point me in the correct direction
for the archives. Thanks


----- Original Message -----
From: John Rood <john@xxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Wednesday, July 19, 2000 5:38 AM
Subject: Re: [cobalt-users] Webalizer .pkg for the Raq3


> On Tue, 18 Jul 2000, Debbie Doerrlamm wrote:
>
> >
> >  >raq. So if you're interrested, give it a swing. You'll find the
package on
> >  >ftp.sfarc.net/pub/webalizer/. Please take a sec or two to read the
README
> >  >first though.
> >
> > John.. a quick Q.. I have the cobalt pkg in and working now.. can I just
> > install you pkg in the GUI will it over write the old?? or must I remove
> > the other pkg 1st?? (and if so.. darn can't find my notes on how to do
that!!)
> >
>
> Hi Debbie,
>
> Packages are supposed to be removable, though this option isn't accessable
> from the gui. This is done by the /usr/local/sbin/cobalt_uninstall script.
> But looking at most uninstall scripts, this prolly won't work. I took a
> peek at the uninstall script that shipped with the cobalt package, and
> indeed, this won't work. Lucky you, my package resembles the cobalt one a
> lot. The only difference i could find is that the cobalt package copies a
> webalizer script directly into /etc/cron.daily, while mine sticks a sort
> like script in /usr/local/bin and only puts a cron file in /etc/cond.d.
>
> For this version of the packages, you only have to rm
> /etc/cron.daily/webalizer.pl and my version should install without any
> problems. Some cruft will be left over from the other package and i
> think the best thing to do is removing this too. Those file would
> be /var/lib/cobalt/webalizer-1.0.md5lst and
> /var/lib/cobalt/uninstallers/webalizer-1.0.uninst. Nothing rm can't handle
> ;)
>
> There's one real but, however... Since the layout of webalizer's
> history file changed, it'll break if you already have stats around from
> the old package. Easiest way around this is removing the stat dirs for all
> your sites, unless you feel like converting all the history files. This
> also takes care of any left .htaccess files (could be a downside though).
> More information on converting from 1.30 to 2.00 can be found on the
> webalizer site (http://www.mrunix.net/webalizer/). One final note; if the
> cobalt package works for you and you're happy with it, why replace it?
> There's this old saying "If it ain't b0rken, don't fix it". My package was
> a very early release is and is apt to some heavy changes (mainly a gui).
> Maybe it's wise to stick to something that actually works :). If you're
> gonna try it anyway i hope it works out of the box and you'll enjoy it.
>
> Best regards,
> John
>
> --
> Hi! I'm a .signature virus! Copy me into your ~/.signature to help me
spread!
> --
> John C. Rood
> UNIX programmer/Database developer/System administrator
> SFARC Networks, The Netherlands - http://www.sfarc.net
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>