RE: CentOS Digest, Vol 23, Issue 30

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]




-----Original Message-----
From: "centos-request@xxxxxxxxxx" <centos-request@xxxxxxxxxx>
To: "centos@xxxxxxxxxx" <centos@xxxxxxxxxx>
Sent: 12/30/06 12:01 PM
Subject: CentOS Digest, Vol 23, Issue 30

Send CentOS mailing list submissions to
	centos@xxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.centos.org/mailman/listinfo/centos
or, via email, send a message with subject or body 'help' to
	centos-request@xxxxxxxxxx

You can reach the person managing the list at
	centos-owner@xxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS digest..."


Today's Topics:

   1. Re: Redhat 5 delayed until march, Centos april then?
      (Karanbir Singh)
   2. RE: Redhat 5 delayed until march, Centos april then? (Drew Weaver)
   3. Re: UPS support on CentOS 4.4 (Scott Silva)
   4. Re: Fwd: How to add a route to a network via 2 gateways.
      (Scott Silva)
   5. Re: Fwd: How to add a route to a network via 2 gateways.
      (Peter Farrow)
   6. Re: Fwd: How to add a route to a network via 2 gateways.
      (Peter Farrow)
   7. Re: Fwd: How to add a route to a network via 2 gateways.
      (Aleksandar Milivojevic)
   8. Fwd:  Fwd: How to add a route to a network via 2
      gateways. (Indunil Jayasooriya)
   9. Re: How to change NIC alias? (Linux Man)
  10. logrotate: how to email logs with mutt? (M. Fioretti)
  11. Re: logrotate: how to email logs with mutt? (Kingsly John)
  12. Re: CentOS 4.5 and  CentOS 5.0 News (William L. Maltby)
  13. Re: CentOS 4.5 and  CentOS 5.0 News (William L. Maltby)
  14. Re: CentOS 4.5 and  CentOS 5.0 News (William L. Maltby)
  15. Re: logrotate: how to email logs with mutt? (M. Fioretti)
  16. Re: CentOS 4.5 and  CentOS 5.0 News (William L. Maltby)
  17. Re: logrotate: how to email logs with mutt? (Kingsly John)


----------------------------------------------------------------------

Message: 1
Date: Fri, 29 Dec 2006 19:14:43 +0000
From: Karanbir Singh <mail-lists@xxxxxxxxx>
Subject: Re:  Redhat 5 delayed until march, Centos april then?
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <45956923.10303@xxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Drew Weaver wrote:
> Its not really a bug, the kernel which comes with the installer doesn't
> support the hardware...
> 
Do you know what kernel version does, and can you point out the patch 
for the driver ? Maybe we can massage it into a driver that works :)


-- 
Karanbir Singh : http://www.karan.org/ : 2522219@icq


------------------------------

Message: 2
Date: Fri, 29 Dec 2006 14:28:37 -0500
From: "Drew Weaver" <drew.weaver@xxxxxxxxxx>
Subject: RE:  Redhat 5 delayed until march, Centos april then?
To: "CentOS mailing list" <centos@xxxxxxxxxx>
Message-ID: <B9ECBF8D89E7684EB63FF250E8788B1942C25C@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain;	charset="US-ASCII"

I know they added support in 2.6.18 for 965/s5000 (ich8).

 ChangeLog-2.6.18-rc1:

commit 19039bd0079f282b1023e61212285b5653e3a8ad
Author: Takashi Iwai
Date: Wed Jun 28 15:52:16 2006 +0200

[ALSA] Add Intel D965 board support

Added the support for Intel D965 boards with STAC9227 codec.

Signed-off-by: Takashi Iwai
Signed-off-by: Jaroslav Kysela 

ChangeLog-2.6.18-rc2:

commit ae2c3860eb18712b71861bb6fc8d7e11e0f79e6d
Author: Auke Kok
Date: Tue Jun 27 09:08:30 2006 -0700

e1000: add ich8lan device ID's

Add the device ID's of the supported ICH8 LAN devices.

Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok 

commit 1f9e7e3d32f7ff3fd3a936fc9ad59770b3d29774
Author: Auke Kok
Date: Tue Jun 27 09:08:26 2006 -0700

e1000: allow user to disable ich8 lock loss workaround

The workaround for the ich8 lock loss problem is only needed for
a very small amount of systems. This adds an option for the user
to disable the workaround.

Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok 

commit cd94dd0b648ceb64ca5e41d9ccfa99c1e30e92ef
Author: Auke Kok
Date: Tue Jun 27 09:08:22 2006 -0700

e1000: integrate ich8 support into driver

This hooks up the ich8 structure into the driver itself.

Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok 

commit d37ea5d56293b7a883d2a993df5d8b9fb660ed3b
Author: Auke Kok
Date: Tue Jun 27 09:08:17 2006 -0700

e1000: add ich8lan core functions

This implements the core new functions needed for ich8's internal
NIC. This includes:

* ich8 specific read/write code
* flash/nvm access code
* software semaphore flag functions
* 10/100 PHY (fe - no gigabit speed) support for low-end versions
* A workaround for a powerdown sequence problem discovered that
affects a small number of motherboard.

Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok 

ChangeLog-2.6.18-rc3:

commit 08f12edc335d24a89ba2f50b0a5b9d12295ce198
Author: Jeff Garzik
Date: Tue Jul 11 11:57:44 2006 -0400

[libata] ata_piix: attempt to fix ICH8 support

Take into account the fact that ICH8 changed the register layout of
the MAP and PCS register bits.

Signed-off-by: Jeff Garzik

-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
Behalf Of Karanbir Singh
Sent: Friday, December 29, 2006 2:15 PM
To: CentOS mailing list
Subject: Re:  Redhat 5 delayed until march, Centos april then?

Drew Weaver wrote:
> Its not really a bug, the kernel which comes with the installer 
> doesn't support the hardware...
> 
Do you know what kernel version does, and can you point out the patch
for the driver ? Maybe we can massage it into a driver that works :)


-- 
Karanbir Singh : http://www.karan.org/ : 2522219@icq
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


------------------------------

Message: 3
Date: Fri, 29 Dec 2006 13:24:52 -0800
From: Scott Silva <ssilva@xxxxxxxxxxxx>
Subject:  Re: UPS support on CentOS 4.4
To: centos@xxxxxxxxxx
Message-ID: <en40va$dba$1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

Edward Diener spake the following on 12/29/2006 7:29 AM:
> peter wrote:
>>
>>
>>
>>> You are right, but this software needs to be manually run for the end
>>> user to find out what is happening.
>>>
>>> What I really want of course is for a visual window to popup whenever
>>> there are A/C problems, and whenever the A/C has lost power and the UPS
>>> battery is getting low.
>>
>>> It is part of apcupsd. I will look at it and see if I can get it going
>>> in CentOS 4.4. Thanks for reminding me of it.
>>
>>
>>
>>
>> I haven't bothered to play with apcupsd just because I don't need to
>> worry
>> about my power where my boxes live, but on the software note, I tend
>> to find
>> far more usefull to have linux software do something intelligent like
>> send me
>> an email when there's a problem so I can just forward that to my cell
>> phone,
>> and end up notified and able to react wherever I happen to be.
> 
> That is a nice feature to have.
> 
>>
>> I don't even see popups on the screen of my workstation, much less
>> anything
>> I might need a UPS on. Why would I want windows software behavior
>> under Linux?
> 
> I don't know what you mean by "windows software behavior" but if I am
> working with the screen in front of me and the A/C power to my UPS goes
> out or the system needs to shut down because the A/C power has been out
> and the UPS battery is running out of power to support my continued
> working, I like to experience some sort of notification when these
> things are happening. Since I am staring at my screen, a visual
> notification seems justified to me. If that seems unusual to you then I
> can only surmise that you use your computer differently than I do.
> Nonetheless, since it's each to their own, a visual notification is what
> I would like to alert me to what is happening.
You always have the constant beeping from the UPS, and the sound of the
inverters humming. Don't depend on the software to be real accurate on the
time remaining, as it is an estimate, and is not always very accurate.
 I usually close what I am doing , saving if needed, as soon as I hear the
damn thing.. I will give it a minute or two, as the building I am in right now
has many short (5 to 10 second) sags every day.

-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!



------------------------------

Message: 4
Date: Fri, 29 Dec 2006 13:34:05 -0800
From: Scott Silva <ssilva@xxxxxxxxxxxx>
Subject:  Re: Fwd: How to add a route to a network via 2
	gateways.
To: centos@xxxxxxxxxx
Message-ID: <en41gk$erb$1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

Indunil Jayasooriya spake the following on 12/29/2006 3:11 AM:
> Hi ,
> 
> I have a network to reach which is 192.168.2.0/24
> . It is a branch of the company. I have currently
> added a route to that network via one gateway ( 192.168.0.254)
>  in following way.
> 
> ip route add 192.168.2.0/24  via 192.168.0.254
> 
> 
> Now, We got another gateway which is 192.168.0.250
> < Now I want to add a route to the same network 
> which is 192.168.2.0/24  via this gateway (
> 192.168.0.250 ) as well.
> 
> Then I will have 2 paths to the same network. One path should be primary
> and the other path  should be backup. everything should go via primary
> path.
> 
> if the primary  path goes down, the backup path should be active.
> 
> That is the purpose of doing this.
> 
> Pls let me know whether it is possible or not?
> 
> if possible, How can I achieve this goal.
> 
When you create a route there is a metric number that does this. But you will
need a routing daemon running to use it. Another possibility would be to have
a script run every 5 minutes in cron that pings the first gateway, and if the
ping fails, change the route. It would also need logic to fix the first route
when the primary gateway starts answering pings again.

-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!



------------------------------

Message: 5
Date: Fri, 29 Dec 2006 21:39:04 +0000
From: Peter Farrow <peter@xxxxxxxxxxx>
Subject: Re:  Fwd: How to add a route to a network via 2
	gateways.
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <45958AF8.3000800@xxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

You can add a second route and weight it as follows:
ip route add equalize 192.168.2.0/24 scope global nexthop via 
192.168.0.254 dev eth0 weight 1 nexthop via 192.168.0.250 dev eth0 weight 1

This assumes that:

both gateways are connected to eth0 on your linux box
You want equal traffic weight down each gateway to the remote network....

Regards

P.



Indunil Jayasooriya wrote:
> Hi ,
>
> I have a network to reach which is *MailScanner warning: numerical 
> links are often malicious:* 192.168.2.0/24 <http://192.168.2.0/24>. It 
> is a branch of the company. I have currently added a route to that 
> network via one gateway ( *MailScanner warning: numerical links are 
> often malicious:* 192.168.0.254 <http://192.168.0.254>) in following way.
>
> ip route add *MailScanner warning: numerical links are often 
> malicious:* 192.168.2.0/24 <http://192.168.2.0/24> via *MailScanner 
> warning: numerical links are often malicious:* 192.168.0.254 
> <http://192.168.0.254>
>
> Now, We got another gateway which is *MailScanner warning: numerical 
> links are often malicious:* 192.168.0.250 <http://192.168.0.250>. Now 
> I want to add a route to the same network  which is *MailScanner 
> warning: numerical links are often malicious:* 192.168.2.0/24 
> <http://192.168.2.0/24> via this gateway (*MailScanner warning: 
> numerical links are often malicious:* 192.168.0.250 
> <http://192.168.0.250>) as well.
>
> Then I will have 2 paths to the same network. One path should be 
> primary and the other path  should be backup. everything should go via 
> primary path.
>
> if the primary  path goes down, the backup path should be active.
>
> That is the purpose of doing this.
>
> Pls let me know whether it is possible or not?
>
> if possible, How can I achieve this goal.
>
>
>
>
>
>
> -- 
> Thank you
> Indunil Jayasooriya
>
> -- 
> This message has been scanned for viruses and
> dangerous content by the *Enhancion* <http://www.enhancion.net/> 
> system scanner,
> and is believed to be clean.
> ------------------------------------------------------------------------
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>   


-- 
This message has been scanned for viruses and
dangerous content by the Enhancion system Scanner
and is believed to be clean.
http://www.enhancion.net



------------------------------

Message: 6
Date: Fri, 29 Dec 2006 21:43:49 +0000
From: Peter Farrow <peter@xxxxxxxxxxx>
Subject: Re:  Fwd: How to add a route to a network via 2
	gateways.
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <45958C15.807@xxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

To achieve the goal of primary path only, you can heavily weight one 
path over the other, some traffic will still spill into the other, you 
can remove the equalize parameter to disable this behaviour,

if you take a look at the linux advanced routing howto there are lots of 
options to play with..

P.

Peter Farrow wrote:
> You can add a second route and weight it as follows:
> ip route add equalize 192.168.2.0/24 scope global nexthop via 
> 192.168.0.254 dev eth0 weight 1 nexthop via 192.168.0.250 dev eth0 
> weight 1
>
> This assumes that:
>
> both gateways are connected to eth0 on your linux box
> You want equal traffic weight down each gateway to the remote network....
>
> Regards
>
> P.
>
>
>
> Indunil Jayasooriya wrote:
>> Hi ,
>>
>> I have a network to reach which is *MailScanner warning: numerical 
>> links are often malicious:* 192.168.2.0/24 <http://192.168.2.0/24>. 
>> It is a branch of the company. I have currently added a route to that 
>> network via one gateway ( *MailScanner warning: numerical links are 
>> often malicious:* 192.168.0.254 <http://192.168.0.254>) in following 
>> way.
>>
>> ip route add *MailScanner warning: numerical links are often 
>> malicious:* 192.168.2.0/24 <http://192.168.2.0/24> via *MailScanner 
>> warning: numerical links are often malicious:* 192.168.0.254 
>> <http://192.168.0.254>
>>
>> Now, We got another gateway which is *MailScanner warning: numerical 
>> links are often malicious:* 192.168.0.250 <http://192.168.0.250>. Now 
>> I want to add a route to the same network  which is *MailScanner 
>> warning: numerical links are often malicious:* 192.168.2.0/24 
>> <http://192.168.2.0/24> via this gateway (*MailScanner warning: 
>> numerical links are often malicious:* 192.168.0.250 
>> <http://192.168.0.250>) as well.
>>
>> Then I will have 2 paths to the same network. One path should be 
>> primary and the other path  should be backup. everything should go 
>> via primary path.
>>
>> if the primary  path goes down, the backup path should be active.
>>
>> That is the purpose of doing this.
>>
>> Pls let me know whether it is possible or not?
>>
>> if possible, How can I achieve this goal.
>>
>>
>>
>>
>>
>>
>> -- 
>> Thank you
>> Indunil Jayasooriya
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by the *Enhancion* <http://www.enhancion.net/> 
>> system scanner,
>> and is believed to be clean.
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>>   
>
>


-- 
This message has been scanned for viruses and
dangerous content by the Enhancion system Scanner
and is believed to be clean.
http://www.enhancion.net



------------------------------

Message: 7
Date: Fri, 29 Dec 2006 16:07:53 -0600
From: Aleksandar Milivojevic <alex@xxxxxxxxxxxxxxx>
Subject: Re:  Fwd: How to add a route to a network via 2
	gateways.
To: centos@xxxxxxxxxx
Message-ID: <20061229160753.1ibh0xbiuck4c8gk@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; DelSp=Yes; format=flowed

Quoting Indunil Jayasooriya <indunil75@xxxxxxxxx>:

> Hi ,
>
> I have a network to reach which is 192.168.2.0/24. It is a branch of the
> company. I have currently added a route to that network via one gateway (
> 192.168.0.254) in following way.
>
> ip route add 192.168.2.0/24 via 192.168.0.254
>
> Now, We got another gateway which is 192.168.0.250. Now I want to add a
> route to the same network  which is 192.168.2.0/24 via this gateway
> (192.168.0.250)
> as well.
>
> Then I will have 2 paths to the same network. One path should be primary and
> the other path  should be backup. everything should go via primary path.
>
> if the primary  path goes down, the backup path should be active.
>
> That is the purpose of doing this.
>
> Pls let me know whether it is possible or not?
>
> if possible, How can I achieve this goal.

One possible solution is to enable one of the routing protocols on  
your routers, instead of using static routing.  For example BGP or  
OSPF.  The routers will than discover which paths to every of the  
networks you have exist and will dynamically change routing rules  
(instead of using static set of rules) as the network connections go  
up and down.  In the way you requested in your question.  It might be  
an overkill for simple network.  But if your network becomes more  
complex in the future, you'll have infrastructure to handle it.   
Another advantage of using standard routing protocol is that they tend  
to be platform independent.  You want to replace that Cisco router  
with Linux router or Linux router with Cisco router.  Guess what, you  
can use BGP or OSPF on both Linux and Cisco based router and your  
configuration is not specific to single type of router anymore.




------------------------------

Message: 8
Date: Sat, 30 Dec 2006 10:49:14 +0530
From: "Indunil Jayasooriya" <indunil75@xxxxxxxxx>
Subject: Fwd:  Fwd: How to add a route to a network via 2
	gateways.
To: peter@xxxxxxxxxxx, "CentOS mailing list" <centos@xxxxxxxxxx>
Message-ID:
	<7ed6b0aa0612292119g3b6c624fn251c454d144fa14d@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

HI Peter,

Interesting in deed. You say that  You can add a second route and weight it
as follows:

ip route add equalize 192.168.2.0/24 scope global nexthop via
192.168.0.254 dev eth0 weight 1 nexthop via 192.168.0.250 dev eth0 weight 1

I want to know whether I can use the above command , when the below command
exists .

ip route add 192.168.2.0/24 via 192.168.0.254

Then I want to know about your second answer which is "To achieve the goal
of primary path only, you can heavily weight one path over the other, some
traffic will still spill into the other, you
can remove the equalize parameter to disable this behaviour "

herein,  what is this "you can heavily weight one path over the other"

When weight 1 and weight 1 , Both paths are equal. If I use weight 1 and
weight 100 , what would be the primary path ? Is it weight 1 ?

Is it the lower number which becomes primary ?

Then , in my case, is the following coomad is right?

ip route add  192.168.2.0/24 scope global nexthop via
192.168.0.254 dev eth0 weight 1 nexthop via 192.168.0.250 dev eth0 weight
100

I guess with the above command that traffc will flow via primary, when it
fails , traffic will flow via secondary.

That is what I need.

 Am I right ? Then can I acheive this goal ?

Thanks
Indunil

---------- Forwarded message ----------
From: Aleksandar Milivojevic <alex@xxxxxxxxxxxxxxx>
Date: Dec 30, 2006 3:37 AM
Subject: Re:  Fwd: How to add a route to a network via 2 gateways.
To: centos@xxxxxxxxxx

Quoting Indunil Jayasooriya <indunil75@xxxxxxxxx>:

> Hi ,
>
> I have a network to reach which is 192.168.2.0/24. It is a branch of the
> company. I have currently added a route to that network via one gateway (
> 192.168.0.254) in following way.
>
> ip route add 192.168.2.0/24 via 192.168.0.254
>
> Now, We got another gateway which is 192.168.0.250. Now I want to add a
> route to the same network  which is 192.168.2.0/24 via this gateway
> (192.168.0.250)
> as well.
>
> Then I will have 2 paths to the same network. One path should be primary
and
> the other path  should be backup. everything should go via primary path.
>
> if the primary  path goes down, the backup path should be active.
>
> That is the purpose of doing this.
>
> Pls let me know whether it is possible or not?
>
> if possible, How can I achieve this goal.

One possible solution is to enable one of the routing protocols on
your routers, instead of using static routing.  For example BGP or
OSPF.  The routers will than discover which paths to every of the
networks you have exist and will dynamically change routing rules
(instead of using static set of rules) as the network connections go
up and down.  In the way you requested in your question.  It might be
an overkill for simple network.  But if your network becomes more
complex in the future, you'll have infrastructure to handle it.
Another advantage of using standard routing protocol is that they tend
to be platform independent.  You want to replace that Cisco router
with Linux router or Linux router with Cisco router.  Guess what, you
can use BGP or OSPF on both Linux and Cisco based router and your
configuration is not specific to single type of router anymore.


_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


-- 
Thank you
Indunil Jayasooriya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos/attachments/20061230/afd24593/attachment-0001.htm

------------------------------

Message: 9
Date: Sat, 30 Dec 2006 03:54:17 -0200
From: "Linux Man" <linuxman.uru@xxxxxxxxx>
Subject: Re:  How to change NIC alias?
To: "CentOS mailing list" <centos@xxxxxxxxxx>
Message-ID:
	<cd66ad610612292154i108e29d1scd22f1992d08b185@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Thanks!
works perfect!

2006/12/28, Barry Brimer <lists@xxxxxxxxxx>:
> > Hello all.
> > I'm installing CentOS 4.4 over a PC with 3 ethernet cards, one onboard
> > (gigabit) and the another two discrete PCI.
> > During installation I have no choice to control who will be eth0, eth1
> > and eth2, but I need that eth0 be the onboard ethernet.
> > In the end of the installation, it turned out to be one of the
> > discrete ethernet eth0.
> > I need to change that alias, so that the actual eth0 become eth1 and vice
> > versa.
> > Thanks a lot
>
> Modify the "/etc/modprobe.conf" files to reflect the drivers you wish to
> use for each interface.  Also change the "HWADDR" directive in the
> interface configuration files which are located in
> "/etc/sysconfig/network-scripts" to match accordingly.
>
> Barry
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>


------------------------------

Message: 10
Date: Sat, 30 Dec 2006 10:39:28 +0100
From: "M. Fioretti" <mfioretti@xxxxxxxxx>
Subject:  logrotate: how to email logs with mutt?
To: centos@xxxxxxxxxx
Message-ID: <20061230093928.GK4190@xxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

Hello,

next week I'll install logrotate on a centos 4.4 server via yum.

The man page says that the default mail command is /bin/mail -s, but
there is no such binary on Centos.

I do have mutt installed, however, so I would like to use it. Ideally,
I would like to have logrotate send logs with mutt as attachments like
this:

 mutt me@xxxxxxxxxxxx -a compressed_log_file -s "here are your log files"

ie send the log as attachment, not email body. But the logrotate man page says:

--mail <command>

        Tells logrotate which command to use when mailing
	logs. This command should accept two arguments: 1) the
        subject of the message, and 2) the recipient.
        The command must then read a message on  standard  input  and
        mail it to the recipient.

so I have not clear how to make it use mutt as I want. Is it OK to say

--mail 'mutt me@xxxxxxxxxxxx -a compressed_log_file -s "here are your log files"'

or will logrotate send the log in the email _body_?

I will check myself the first time logrotate runs, but I thought it
would be nice to know if others are already usign mutt with logrotate
and document here on the list the whole setup.

Thanks,
M.




------------------------------

Message: 11
Date: Sat, 30 Dec 2006 17:15:24 +0530
From: Kingsly John <member+centos@xxxxxxxxxxx>
Subject: Re:  logrotate: how to email logs with mutt?
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <20061230114524.GA22252@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

+++ M. Fioretti [2006-12-30 10:39:28]:

> Hello,
> 
> next week I'll install logrotate on a centos 4.4 server via yum.
> 
> The man page says that the default mail command is /bin/mail -s, but
> there is no such binary on Centos.

yum install mailx

Kingsly

-- 
---------------------------------------------------------------------------
     Kingsly At Users Dot SourceForge Dot Net  -- http://kingsly.org/
---------------------------------------------------------------------------


------------------------------

Message: 12
Date: Sat, 30 Dec 2006 08:28:59 -0500
From: "William L. Maltby" <CentOS4Bill@xxxxxxxxxxxx>
Subject: Re:  CentOS 4.5 and  CentOS 5.0 News
To: CentOS General List <centos@xxxxxxxxxx>
Message-ID: <1167485339.5372.11.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

On Fri, 2006-12-29 at 10:37 -0500, fredex wrote:
> On Fri, Dec 29, 2006 at 01:41:54PM +0000, Josh Donovan wrote:
> > Hi,
> > 
> > I use CentOS as a firewall/proxy/webserver/fileserver
> > in my small network.<snip> ...
> > 20 GB, pentium II with only 128 MB RAM.
> > 
> > <snip>

> Not directly answering your question, but...
> 
> You may wish to investigate one of the small standalone firewall
> distributions such as Smoothwall, IPCop, or m0n0wall (bsd-based).
> They will all easily run in 128mb, and are easy to configure.
> They are all easy to install. 
> 
> M0n0wall looks intriguing, I may give it a try here someday,... it runs
> from non-writable media such as a CD and saves config on a floppy. It
> can be run from a hard drive or a flash memory card of some sort too.
> The obvious advantage is that if someone cracks the machine they can't
> do any damage (to it, directly) because it's not writable.
> 
> And you really shouldn't be running web- or file-servers on your firewall,
> the more stuff running on it the more opportunities you present for an
> evil person/entity to crack it.
> 
> I'd suggest using one of the above then put another machine in a DMZ
> to do web server duty (if it is supposed to be externally visible--
> otherwise put it on another machine INSIDE the firewall on the "green"
> (allegedly safe) network).
> 
> I'm running Smoothwall Express 2.0 on my old K6-2/500 machine with
> 128MB of memory and a 3 or 4 gig drive. It just runs and runs and runs
> and doesn't come anywhere near using up all the memory. Before that
> box became available I ran it on things similar to P90 or AMD K5, both
> around 90-100 Mhz for several years with 64MB of ram and it ran just
> fine on those machines too.

I second all Fred said. I have a 200MHz Pentium w/96MB running IPCop
(1.11 now) and it just hums (eliminating fans would eliminate the "hums"
too!  :)

But, I have also installed it (for test/backup) on my wife's discarded
Aptiva w/ a real 486 and very little memory (I don't recall how much,
whatever came from the factory... 32MB, 64MB, 128MB?).

Also on an AMD 486 clone (x586?) 100MHz with 36MB of memory.

Only differences observed seem related to half/full duplex nature of the
NICs and raw speed. With my cable being in the "boonies" and a stock
Toshiba cable model, good sites get me 600-700 kChars/sec on the
Pentium, appx. 530K/sec on the AMD and 460K/sec on the Aptiva.

With that in hand, Aleksandr's staple, $20 machinces, should fit in your
scenario very nicely. Like him, I have a bunch  of those (even some $10
ones - 386SX comes to mind). Find justification for their continued
existence seems to be my biggest problem! :P

> 
> Fred
> <snip sig stuff>

HTH
--
Bill



------------------------------

Message: 13
Date: Sat, 30 Dec 2006 08:36:31 -0500
From: "William L. Maltby" <CentOS4Bill@xxxxxxxxxxxx>
Subject: Re:  CentOS 4.5 and  CentOS 5.0 News
To: CentOS General List <centos@xxxxxxxxxx>
Message-ID: <1167485791.5372.21.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

On Fri, 2006-12-29 at 10:37 -0500, fredex wrote:
> On Fri, Dec 29, 2006 at 01:41:54PM +0000, Josh Donovan wrote:
> > Hi,
> > 
> > I use CentOS as a firewall/proxy/webserver/fileserver
> > in my small network.<snip>... 20 GB, pentium II with only 128 MB RAM.
> > 
> ><snip>


> Not directly answering your question, but...
> 
> You may wish to investigate one of the small standalone firewall
> distributions such as Smoothwall, IPCop, or m0n0wall (bsd-based).
> They will all easily run in 128mb, and are easy to configure.
> They are all easy to install. 
> 
> M0n0wall looks intriguing, I may give it a try here someday,... it runs
> from non-writable media such as a CD and saves config on a floppy. It
> can be run from a hard drive or a flash memory card of some sort too.
> The obvious advantage is that if someone cracks the machine they can't
> do any damage (to it, directly) because it's not writable.
> 
> And you really shouldn't be running web- or file-servers on your firewall,
> the more stuff running on it the more opportunities you present for an
> evil person/entity to crack it.
> 
> I'd suggest using one of the above then put another machine in a DMZ
> to do web server duty (if it is supposed to be externally visible--
> otherwise put it on another machine INSIDE the firewall on the "green"
> (allegedly safe) network).
> 
> I'm running Smoothwall Express 2.0 on my old K6-2/500 machine with
> 128MB of memory and a 3 or 4 gig drive. It just runs and runs and runs
> and doesn't come anywhere near using up all the memory. Before that
> box became available I ran it on things similar to P90 or AMD K5, both
> around 90-100 Mhz for several years with 64MB of ram and it ran just
> fine on those machines too.

I second all Fred says. I have IPCop on 200MHz Pentium with 96MB. Runs
steady and fast enough (good sites appx. 700K chars/sec. Cable and in
the boonies responsible for that).

I have also run it on my wifes discarded Aptiva (486 and 64MB? 32MB?)
and my AMD "486 clone", x586 100MHz 36MB. Only difference is speed.
Aptiva about 430K chars/sec, AMD about 510K chars/sec.

Like Aleksandr, I'm loaded with old used ceapo machines too (386SX
anyone?). If you can get a $20 machain (and one for backup?) you would
be making a wise investment, IMO, by having a firewall-dedicated node
separate from your "server/ws".

> 
> Fred
> <snip sig stuff>

HTH
--
Bill



------------------------------

Message: 14
Date: Sat, 30 Dec 2006 08:37:24 -0500
From: "William L. Maltby" <CentOS4Bill@xxxxxxxxxxxx>
Subject: Re:  CentOS 4.5 and  CentOS 5.0 News
To: CentOS General List <centos@xxxxxxxxxx>
Message-ID: <1167485844.5372.22.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

On Fri, 2006-12-29 at 10:37 -0500, fredex wrote:
> On Fri, Dec 29, 2006 at 01:41:54PM +0000, Josh Donovan wrote:
> > Hi,
> > 
> > I use CentOS as a firewall/proxy/webserver/fileserver
> > in my small network. As the small-spec machine with
> > CentOS is heavily loaded/used I can't afford downtime.
> > 20 GB, pentium II with only 128 MB RAM.
> > 
> > However I want to know the news on 4.5 is it due soon?
> > Can I gain more by running CentOS 3.x range on such an
> > old machine like mine?
> > 
> > Will CentOS 5.0 mean you need a minimum of 512 RAM?
> > What is the latest on this?
> > 
> > Are there any addons for CentOS such as
> > squidguard/dansguardian etc? that can assist in
> > parental controls?
> > 
> 
> Not directly answering your question, but...
> 
> You may wish to investigate one of the small standalone firewall
> distributions such as Smoothwall, IPCop, or m0n0wall (bsd-based).
> They will all easily run in 128mb, and are easy to configure.
> They are all easy to install. 
> 
> M0n0wall looks intriguing, I may give it a try here someday,... it runs
> from non-writable media such as a CD and saves config on a floppy. It
> can be run from a hard drive or a flash memory card of some sort too.
> The obvious advantage is that if someone cracks the machine they can't
> do any damage (to it, directly) because it's not writable.
> 
> And you really shouldn't be running web- or file-servers on your firewall,
> the more stuff running on it the more opportunities you present for an
> evil person/entity to crack it.
> 
> I'd suggest using one of the above then put another machine in a DMZ
> to do web server duty (if it is supposed to be externally visible--
> otherwise put it on another machine INSIDE the firewall on the "green"
> (allegedly safe) network).
> 
> I'm running Smoothwall Express 2.0 on my old K6-2/500 machine with
> 128MB of memory and a 3 or 4 gig drive. It just runs and runs and runs
> and doesn't come anywhere near using up all the memory. Before that
> box became available I ran it on things similar to P90 or AMD K5, both
> around 90-100 Mhz for several years with 64MB of ram and it ran just
> fine on those machines too.
> 
> Fred
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos



------------------------------

Message: 15
Date: Sat, 30 Dec 2006 13:29:45 +0100
From: "M. Fioretti" <mfioretti@xxxxxxxxx>
Subject: Re:  logrotate: how to email logs with mutt?
To: centos@xxxxxxxxxx
Message-ID: <20061230122945.GY4190@xxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

On Sat, Dec 30, 2006 17:15:24 PM +0530, Kingsly John
(member+centos@xxxxxxxxxxx) wrote:

> > next week I'll install logrotate on a centos 4.4 server via yum.
> > The man page says that the default mail command is /bin/mail -s, but
> > there is no such binary on Centos.
> 
> yum install mailx

Thanks. I _will_ do it if there really is no mutt solution, but I'd
rather avoid it to keep the number of packages as small as possible,
that's why I asked: since I already _have_ to have mutt on that box
anyway...

Ciao,
M.




------------------------------

Message: 16
Date: Sat, 30 Dec 2006 08:45:25 -0500
From: "William L. Maltby" <CentOS4Bill@xxxxxxxxxxxx>
Subject: Re:  CentOS 4.5 and  CentOS 5.0 News
To: CentOS General List <centos@xxxxxxxxxx>
Message-ID: <1167486325.7590.1.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

On Sat, 2006-12-30 at 08:37 -0500, William L. Maltby wrote:
> <snip>

Sorry about the dupes! I thought the replies had "aborted". Maybe time
to get a pot of coffee involved in the process improvement process! :P

--
Bill



------------------------------

Message: 17
Date: Sat, 30 Dec 2006 20:43:48 +0530
From: Kingsly John <member+centos@xxxxxxxxxxx>
Subject: Re:  logrotate: how to email logs with mutt?
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <20061230151348.GB22252@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

+++ M. Fioretti [2006-12-30 13:29:45]:

> On Sat, Dec 30, 2006 17:15:24 PM +0530, Kingsly John
> (member+centos@xxxxxxxxxxx) wrote:
> 
> > > next week I'll install logrotate on a centos 4.4 server via yum.
> > > The man page says that the default mail command is /bin/mail -s, but
> > > there is no such binary on Centos.
> > 
> > yum install mailx
> 
> Thanks. I _will_ do it if there really is no mutt solution, but I'd
> rather avoid it to keep the number of packages as small as possible,
> that's why I asked: since I already _have_ to have mutt on that box
> anyway...

mutt -x  <-- will enable compatibility with the "mail" command

"mail" is a system command (it's /bin/mail and not /usr/bin/mail) .. and lots
of programs expect it to be present.

I don't know how you don't have the mail command on your system because it's
needed by stuff like cron/at etc too.(or even logrotate for that matter)

Installing mailx is the best solution, your argument of not wanting to
install extra packages doesn't exactly hold true in this case.

In all likelihood you currently have a broken system where you don't get any
notification when cron/at jobs fail etc.

Kingsly

-- 
---------------------------------------------------------------------------
     Kingsly At Users Dot SourceForge Dot Net  -- http://kingsly.org/
---------------------------------------------------------------------------


------------------------------

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


End of CentOS Digest, Vol 23, Issue 30
**************************************

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux