On Tue, Apr 27, 2010 at 2:52 PM, Patrick Chemla
wrote:
> You can put whatever you want in the script. I am monitoring different parts
> of the servers.
>
> Extract:
>
> # Identify the server by the last digit of his IP
> ip3d=`/sbin/ifconfig| grep Bcast|grep 10.0.0|cut -d":" -f2 | cut -d" "
> -f1|
Le 27/04/2010 15:27, Israel Garcia a écrit :
could you share the script with us?
You can put whatever you want in the script. I am monitoring different
parts of the servers.
Extract:
# Identify the server by the last digit of his IP
ip3d=`/sbin/ifconfig| grep Bcast|grep 10.0.0|cut -d":
>>
>> Send log from all nodes to a central log server. Use rsyslogd with RELP to
>> get
>> reliability. Use rsyslog log templates to cut down on bandwidth usage if
>> Postfix log is to verbose.
>>
>
> I am also running a big number of servers. To avoid heavy load on the
> network and on the central
Le 27/04/2010 10:54, Patrick Ben Koetter a écrit :
* Israel Garcia:
> I have about 20 debian servers send all mail through a loadbalancer
> (haproxy) with 2backend smarthosts which send emails to internet. I
> have pflogsumm running only on every smarhost. As every smarthost see
> on IP
* Israel Garcia :
> I have about 20 debian servers send all mail through a loadbalancer
> (haproxy) with 2backend smarthosts which send emails to internet. I
> have pflogsumm running only on every smarhost. As every smarthost see
> on IP source (haproxy) I can not get email stats from every debian
I have about 20 debian servers send all mail through a loadbalancer
(haproxy) with 2backend smarthosts which send emails to internet. I
have pflogsumm running only on every smarhost. As every smarthost see
on IP source (haproxy) I can not get email stats from every debian
server. Questions: How ca
