Re: cron/logrotate

[Jake Morrison <jake_morrison@example.com>]

Jc,

--- Jean-Christian Imbeault <jean_christian@example.com> wrote:
> >rotatelogs comes with the source.
> >You can build it separately and use it with your RPM based system.
> 
> Done that :) Installed 1.3.20 on a test machine jsut to see what I'm
> up against.
> 
> >  $ ./configure --prefix=PREFIX
> >  $ make
> >  $./configure --prefix=PREFIX make install
> >  $ PREFIX/bin/apachectl start
> >
> >Now that wasn't so painful, was it :-)
> 
> Not at all;) But is my 1.3.12 conf file compatible?
> Compiling/installing the source was easy. I'm just 
> worried about library conflicts and wether
> or not the conf file will still work.

Generally speaking, yes. Apache is pretty good about backwards
compatibility, so I would expect that any 1.3.x config file
would work with 1.3.20. 

The only issue is how messed up the Red Hat config file is. :-)
It is probably best to just use the new one and make any
necessary changes. 

> 
> Also, would an "rpm -e apache-1.2.12" before the new installation
> cause any problems? 
> How about *after* the new installation; 
> doing it after is preferable so that I can switch over 
> quickly and minimize the downtime.

I would keep the old and new installations running simultaneously
until you are sure things are working properly.

What you should do is install the new Apache in a directory
different from the Red Hat default. /usr/local/apache is
pretty common (i.e. "configure --prefix=/usr/local/apache") 

Edit the httpd.conf file to specify a non-standard port
for testing (e.g. 8080). Change the "DocumentRoot" directive
to point to point to where your files are now. This way it
will read documents from your existing tree. 

You will also have to change the access control specification
further down in the file to match this directory. You 
will likely also have to do the same for the CGI directory,
or just copy any CGI programs over to the new cgi-bin directory.

You should then be able to start up the new httpd by saying
"/usr/local/apache/bin/apachectl start"
Point your browser to port 8080 and see if things work.

This assumes that your Apache installation is pretty generic.
If not, you may need to tweak things in the new installation
to match the old. When you are done, you will know what's
going on and you will be in control :-)

If things are working fine with the new Apache, you can
switch over to the new by changing it to port 80.
You can then uninstall the Apache RPM. You might want
to move the document/CGI files somewhere more planned,
as well. 

You may want to install nifty things like PHP and
mod_perl/mod_ruby/mod_snake to make your developers happy. 
That is lots of fun all by itself.

> 
> >There is also a logrotate man page.
> 
> For some reason that didn't get installed automagically. 
> The page is there 
> under "/usr/local/apache/man/man8/rotatelogs.8" but a man rotatelog
> brings up nothing. 
> I had to man it manually. 

You could always copy it yourself, or set MANPATH.

> It's helpful but doesn't say how to 
> set up rotatelogs to make only 4 copies, but I'm looking into it.
> 

You can use a separate script for that, if you like. The key
is that now it won't affect the existing web server processes.

Jake


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/