Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux Virtual Server: Users

[lvs-users] emailalertperiod configuration option

 

 

Linux Virtual Server users RSS feed   Index | Next | Previous | View Threaded


anthony at duck

Nov 10, 2009, 10:46 PM

Post #1 of 7 (918 views)
Permalink
[lvs-users] emailalertperiod configuration option

I wrote a small patch against the latest (as of yesterday) unreleased tree in the mercurial repository.

It requires another CPAN dependency. The Time::Period perl module is used for defining the time period(s) for sending email alerts.

It currently only a per service option
The configuration option is emailalertperiod.

if not defined it has a default of
wd {Mon-Fri} hr {12am-12pm}

period configuration options are explained in the Time::Period man page.
or you can check them out here
http://search.cpan.org/~pryan/Period-1.20/Period.pm

I did some testing and it seems to work correctly. Let me know what you think.


anthony





--- ldirectord 2009-11-10 04:42:45.000000000 -0500
+++ ldirectord.new 2009-11-11 01:09:36.000000000 -0500
@@ -260,6 +260,14 @@
Default: 0


+B<emailalertperiod = >I<time period>
+
+A valid time period as specified by the Time::Period perl module for sending
+email alerts.
+
+Default: wd {Mon-Fri} hr {12am-12pm}
+
+
B<emailalertstatus = >B<all>|B<none>|B<starting>|B<running>|B<stopping>|B<reloading>,...

Comma delimited list of server states in which email alerts should be sent.
@@ -737,6 +745,7 @@
$FORKING
$EMAILALERT
$EMAILALERTFREQ
+ $EMAILALERTPERIOD
$EMAILALERTSTATUS
$EMAILALERTFROM
$SMTP
@@ -811,6 +820,7 @@
use Pod::Usage;
#use English;
#use Time::HiRes qw( gettimeofday tv_interval );
+use Time::Period;
use Socket;
use Socket6;
use Sys::Hostname;
@@ -1229,6 +1239,7 @@
$EMAILALERT = "";
$EMAILALERTFREQ = 0;
$EMAILALERTFROM = undef;
+ $EMAILALERTPERIOD = "wd {Mon-Sun} hr {12am-12pm}";
$EMAILALERTSTATUS = $DAEMON_STATUS_ALL;
$FAILURECOUNT = 1;
$FALLBACK = undef;
@@ -1257,6 +1268,7 @@
&config_error(0, "can not open file $CONFIG");
my $line = 0;
my $linedata;
+ my $alertperiod;
while(<CFGFILE>) {
$line++;
$linedata = $_;
@@ -1510,6 +1522,10 @@
} elsif ($rcmd =~ /^emailalertfreq\s*=\s*(\d*)/) {
$1 =~ /(\d+)/ or &config_error($line, "invalid email alert frequency");
$vsrv{emailalertfreq} = $1;
+ } elsif ($rcmd =~ /^emailalertperiod\s*=\s*(.*)/) {
+ $alertperiod=$1;
+ (inPeriod(time, $alertperiod) != "-1") or &config_error($line, "invalid email alert period");
+ $vsrv{emailalertperiod} = $1;
} elsif ($rcmd =~ /^emailalertstatus\s*=\s*(.*)/) {
$vsrv{emailalertstatus} = &parse_emailalertstatus($line, $1);
} elsif ($rcmd =~ /^monitorfile\s*=\s*\"(.*)\"/ or
@@ -1643,6 +1659,11 @@
$1 =~ /(\d+)/ or &config_error($line,
"invalid email alert frequency");
$EMAILALERTFREQ = $1;
+ } elsif ($linedata =~ /^emailalertperiod\s*=\s*(.*)/) {
+ $alertperiod=$1;
+ (inPeriod(time, $alertperiod) != "-1") or &config_error($line,
+ "invalid email alert period");
+ $EMAILALERTPERIOD = $1;
} elsif ($linedata =~ /^emailalertstatus\s*=\s*(.*)/) {
$EMAILALERTSTATUS = &parse_emailalertstatus($line, $1);
} elsif ($linedata =~ /^emailalertfrom\s*=\s*(.*)/) {
@@ -4193,11 +4214,18 @@
my $status = 0;
my $to_addr;
my $frequency;
+ my $alertperiod;
my $virtual_str;
my $id;
my $statusfilter;
my $smtp_server;

+ $alertperiod = defined $v->{emailalertperiod} ?
+ $v->{emailalertperiod} : $EMAILALERTPERIOD;
+ if (inPeriod(time, $alertperiod) != "1" ){
+ &ld_log("skipping email alert - alert period:".$alertperiod);
+ return 0;
+ }
$frequency = defined $v->{emailalertfreq} ? $v->{emailalert} :
$EMAILALERTFREQ;

@@ -4226,7 +4254,7 @@
$smtp_server = defined $v->{smtp} ? $v->{smtp} :
$SMTP;

- &ld_log("emailalert: $subject");
+ &ld_log("emailalert($alertperiod): $subject");
if (defined $smtp_server) {
$status = &ld_emailalert_net_smtp($smtp_server, $to_addr, $subject);
}


_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


anthony at duck

Nov 10, 2009, 11:37 PM

Post #2 of 7 (884 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

i just realized a mistake in my previous email

the default emailalertperiod is actually set for
wd {Mon-Sun} hr {12am-12pm}

and not
wd {Mon-Fri} hr {12am-12pm}

I just put it incorrectly in my email and since i copied and pasted into the email from the help section of the patch that is also wrong, but the variable in the script is set correctly, so it still defaults to alerting 7 days a week. If its patched into the tree, it needs to be corrected in the
help section.

anthony


Anthony Ciaravalo wrote:
> I wrote a small patch against the latest (as of yesterday) unreleased tree in the mercurial repository.
>
> It requires another CPAN dependency. The Time::Period perl module is used for defining the time period(s) for sending email alerts.
>
> It currently only a per service option
> The configuration option is emailalertperiod.
>
> if not defined it has a default of
> wd {Mon-Fri} hr {12am-12pm}
>
> period configuration options are explained in the Time::Period man page.
> or you can check them out here
> http://search.cpan.org/~pryan/Period-1.20/Period.pm
>
> I did some testing and it seems to work correctly. Let me know what you think.
>
>
> anthony
>
>
>
>
>
> --- ldirectord 2009-11-10 04:42:45.000000000 -0500
> +++ ldirectord.new 2009-11-11 01:09:36.000000000 -0500
> @@ -260,6 +260,14 @@
> Default: 0
>
>
> +B<emailalertperiod = >I<time period>
> +
> +A valid time period as specified by the Time::Period perl module for sending
> +email alerts.
> +
> +Default: wd {Mon-Fri} hr {12am-12pm}
> +
> +
> B<emailalertstatus = >B<all>|B<none>|B<starting>|B<running>|B<stopping>|B<reloading>,...
>
> Comma delimited list of server states in which email alerts should be sent.
> @@ -737,6 +745,7 @@
> $FORKING
> $EMAILALERT
> $EMAILALERTFREQ
> + $EMAILALERTPERIOD
> $EMAILALERTSTATUS
> $EMAILALERTFROM
> $SMTP
> @@ -811,6 +820,7 @@
> use Pod::Usage;
> #use English;
> #use Time::HiRes qw( gettimeofday tv_interval );
> +use Time::Period;
> use Socket;
> use Socket6;
> use Sys::Hostname;
> @@ -1229,6 +1239,7 @@
> $EMAILALERT = "";
> $EMAILALERTFREQ = 0;
> $EMAILALERTFROM = undef;
> + $EMAILALERTPERIOD = "wd {Mon-Sun} hr {12am-12pm}";
> $EMAILALERTSTATUS = $DAEMON_STATUS_ALL;
> $FAILURECOUNT = 1;
> $FALLBACK = undef;
> @@ -1257,6 +1268,7 @@
> &config_error(0, "can not open file $CONFIG");
> my $line = 0;
> my $linedata;
> + my $alertperiod;
> while(<CFGFILE>) {
> $line++;
> $linedata = $_;
> @@ -1510,6 +1522,10 @@
> } elsif ($rcmd =~ /^emailalertfreq\s*=\s*(\d*)/) {
> $1 =~ /(\d+)/ or &config_error($line, "invalid email alert frequency");
> $vsrv{emailalertfreq} = $1;
> + } elsif ($rcmd =~ /^emailalertperiod\s*=\s*(.*)/) {
> + $alertperiod=$1;
> + (inPeriod(time, $alertperiod) != "-1") or &config_error($line, "invalid email alert period");
> + $vsrv{emailalertperiod} = $1;
> } elsif ($rcmd =~ /^emailalertstatus\s*=\s*(.*)/) {
> $vsrv{emailalertstatus} = &parse_emailalertstatus($line, $1);
> } elsif ($rcmd =~ /^monitorfile\s*=\s*\"(.*)\"/ or
> @@ -1643,6 +1659,11 @@
> $1 =~ /(\d+)/ or &config_error($line,
> "invalid email alert frequency");
> $EMAILALERTFREQ = $1;
> + } elsif ($linedata =~ /^emailalertperiod\s*=\s*(.*)/) {
> + $alertperiod=$1;
> + (inPeriod(time, $alertperiod) != "-1") or &config_error($line,
> + "invalid email alert period");
> + $EMAILALERTPERIOD = $1;
> } elsif ($linedata =~ /^emailalertstatus\s*=\s*(.*)/) {
> $EMAILALERTSTATUS = &parse_emailalertstatus($line, $1);
> } elsif ($linedata =~ /^emailalertfrom\s*=\s*(.*)/) {
> @@ -4193,11 +4214,18 @@
> my $status = 0;
> my $to_addr;
> my $frequency;
> + my $alertperiod;
> my $virtual_str;
> my $id;
> my $statusfilter;
> my $smtp_server;
>
> + $alertperiod = defined $v->{emailalertperiod} ?
> + $v->{emailalertperiod} : $EMAILALERTPERIOD;
> + if (inPeriod(time, $alertperiod) != "1" ){
> + &ld_log("skipping email alert - alert period:".$alertperiod);
> + return 0;
> + }
> $frequency = defined $v->{emailalertfreq} ? $v->{emailalert} :
> $EMAILALERTFREQ;
>
> @@ -4226,7 +4254,7 @@
> $smtp_server = defined $v->{smtp} ? $v->{smtp} :
> $SMTP;
>
> - &ld_log("emailalert: $subject");
> + &ld_log("emailalert($alertperiod): $subject");
> if (defined $smtp_server) {
> $status = &ld_emailalert_net_smtp($smtp_server, $to_addr, $subject);
> }
>
>
> _______________________________________________
> Please read the documentation before posting - it's available at:
> http://www.linuxvirtualserver.org/
>
> LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
> Send requests to lvs-users-request [at] LinuxVirtualServer
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


anthony at duck

Nov 10, 2009, 11:48 PM

Post #3 of 7 (884 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

I guess I should probably set the default time period for 24 hours and not just 12 hours. I think that would be something like hr {12am-11am}. Looking at the documentation for time::period, it covers up to the 59th minute of the hour when doing an hour followed by am or pm.

Also, what are the thoughts of having the configuration option be exclusive instead of inclusive? So instead of defining when it sends emails, define when it will not send email? Its easy enough of a change.

anthony



Anthony Ciaravalo wrote:
> i just realized a mistake in my previous email
>
> the default emailalertperiod is actually set for
> wd {Mon-Sun} hr {12am-12pm}
>
> and not
> wd {Mon-Fri} hr {12am-12pm}
>
> I just put it incorrectly in my email and since i copied and pasted into the email from the help section of the patch that is also wrong, but the variable in the script is set correctly, so it still defaults to alerting 7 days a week. If its patched into the tree, it needs to be corrected in the
> help section.
>
> anthony
>
>
> Anthony Ciaravalo wrote:
>> I wrote a small patch against the latest (as of yesterday) unreleased tree in the mercurial repository.
>>
>> It requires another CPAN dependency. The Time::Period perl module is used for defining the time period(s) for sending email alerts.
>>
>> It currently only a per service option
>> The configuration option is emailalertperiod.
>>
>> if not defined it has a default of
>> wd {Mon-Fri} hr {12am-12pm}
>>
>> period configuration options are explained in the Time::Period man page.
>> or you can check them out here
>> http://search.cpan.org/~pryan/Period-1.20/Period.pm
>>
>> I did some testing and it seems to work correctly. Let me know what you think.
>>
>>
>> anthony
>>
>>
>>
>>
>>
>> --- ldirectord 2009-11-10 04:42:45.000000000 -0500
>> +++ ldirectord.new 2009-11-11 01:09:36.000000000 -0500
>> @@ -260,6 +260,14 @@
>> Default: 0
>>
>>
>> +B<emailalertperiod = >I<time period>
>> +
>> +A valid time period as specified by the Time::Period perl module for sending
>> +email alerts.
>> +
>> +Default: wd {Mon-Fri} hr {12am-12pm}
>> +
>> +
>> B<emailalertstatus = >B<all>|B<none>|B<starting>|B<running>|B<stopping>|B<reloading>,...
>>
>> Comma delimited list of server states in which email alerts should be sent.
>> @@ -737,6 +745,7 @@
>> $FORKING
>> $EMAILALERT
>> $EMAILALERTFREQ
>> + $EMAILALERTPERIOD
>> $EMAILALERTSTATUS
>> $EMAILALERTFROM
>> $SMTP
>> @@ -811,6 +820,7 @@
>> use Pod::Usage;
>> #use English;
>> #use Time::HiRes qw( gettimeofday tv_interval );
>> +use Time::Period;
>> use Socket;
>> use Socket6;
>> use Sys::Hostname;
>> @@ -1229,6 +1239,7 @@
>> $EMAILALERT = "";
>> $EMAILALERTFREQ = 0;
>> $EMAILALERTFROM = undef;
>> + $EMAILALERTPERIOD = "wd {Mon-Sun} hr {12am-12pm}";
>> $EMAILALERTSTATUS = $DAEMON_STATUS_ALL;
>> $FAILURECOUNT = 1;
>> $FALLBACK = undef;
>> @@ -1257,6 +1268,7 @@
>> &config_error(0, "can not open file $CONFIG");
>> my $line = 0;
>> my $linedata;
>> + my $alertperiod;
>> while(<CFGFILE>) {
>> $line++;
>> $linedata = $_;
>> @@ -1510,6 +1522,10 @@
>> } elsif ($rcmd =~ /^emailalertfreq\s*=\s*(\d*)/) {
>> $1 =~ /(\d+)/ or &config_error($line, "invalid email alert frequency");
>> $vsrv{emailalertfreq} = $1;
>> + } elsif ($rcmd =~ /^emailalertperiod\s*=\s*(.*)/) {
>> + $alertperiod=$1;
>> + (inPeriod(time, $alertperiod) != "-1") or &config_error($line, "invalid email alert period");
>> + $vsrv{emailalertperiod} = $1;
>> } elsif ($rcmd =~ /^emailalertstatus\s*=\s*(.*)/) {
>> $vsrv{emailalertstatus} = &parse_emailalertstatus($line, $1);
>> } elsif ($rcmd =~ /^monitorfile\s*=\s*\"(.*)\"/ or
>> @@ -1643,6 +1659,11 @@
>> $1 =~ /(\d+)/ or &config_error($line,
>> "invalid email alert frequency");
>> $EMAILALERTFREQ = $1;
>> + } elsif ($linedata =~ /^emailalertperiod\s*=\s*(.*)/) {
>> + $alertperiod=$1;
>> + (inPeriod(time, $alertperiod) != "-1") or &config_error($line,
>> + "invalid email alert period");
>> + $EMAILALERTPERIOD = $1;
>> } elsif ($linedata =~ /^emailalertstatus\s*=\s*(.*)/) {
>> $EMAILALERTSTATUS = &parse_emailalertstatus($line, $1);
>> } elsif ($linedata =~ /^emailalertfrom\s*=\s*(.*)/) {
>> @@ -4193,11 +4214,18 @@
>> my $status = 0;
>> my $to_addr;
>> my $frequency;
>> + my $alertperiod;
>> my $virtual_str;
>> my $id;
>> my $statusfilter;
>> my $smtp_server;
>>
>> + $alertperiod = defined $v->{emailalertperiod} ?
>> + $v->{emailalertperiod} : $EMAILALERTPERIOD;
>> + if (inPeriod(time, $alertperiod) != "1" ){
>> + &ld_log("skipping email alert - alert period:".$alertperiod);
>> + return 0;
>> + }
>> $frequency = defined $v->{emailalertfreq} ? $v->{emailalert} :
>> $EMAILALERTFREQ;
>>
>> @@ -4226,7 +4254,7 @@
>> $smtp_server = defined $v->{smtp} ? $v->{smtp} :
>> $SMTP;
>>
>> - &ld_log("emailalert: $subject");
>> + &ld_log("emailalert($alertperiod): $subject");
>> if (defined $smtp_server) {
>> $status = &ld_emailalert_net_smtp($smtp_server, $to_addr, $subject);
>> }
>>
>>
>> _______________________________________________
>> Please read the documentation before posting - it's available at:
>> http://www.linuxvirtualserver.org/
>>
>> LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
>> Send requests to lvs-users-request [at] LinuxVirtualServer
>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>
> _______________________________________________
> Please read the documentation before posting - it's available at:
> http://www.linuxvirtualserver.org/
>
> LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
> Send requests to lvs-users-request [at] LinuxVirtualServer
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


eric.robinson at psmnv

Nov 11, 2009, 7:11 AM

Post #4 of 7 (879 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

> Also, what are the thoughts of having the configuration option
> be exclusive instead

Inclusive or exclusive works equally well for me. It'll be a few days
before I can upgrade my ldirectord to the current version and start
testing...

--
Eric Robinson




Disclaimer - November 11, 2009
This email and any files transmitted with it are confidential and intended solely for LinuxVirtualServer.org users mailing list.. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management and Physician's Managed Care. Warning: Although Physician Select Management and Physician's Managed Care have taken reasonable precautions to ensure no viruses are present in this email, the companies cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


anthony at duck

Nov 11, 2009, 7:43 AM

Post #5 of 7 (878 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

ok.

Reading through the documentation for Time::Period again, I think the best way to cover the 24 hour period is probably to just use
hr {0-23}
which covers from 0 hour through 23:59:59

since
"v isn't a point in time. In the context of the hour scale, 9 specifies the time period from 9:00:00 am to 9:59:59 am"

In one section it states
"For the range specification v-v, if the second value is larger than the first value, the range wraps around unless the scale specification is year."

then further down it says,
"To specify the morning, use hour { 12am-11am }"

but I think that only wraps around for am only; not through pm and back to am.

so that means the default variable $EMAILALERTPERIOD setting should be
wd {Mon-Sun} hr {0-23}

or wd {Sun-Sat} hr {0-23}, if the preference is for starting the week on sunday.

I think using
wd {Mon-Sun} hr {12am-11am}, wd {Mon-Sun} hr {12pm-11pm}

would also work for covering am and pm, since you can specify multiple time periods

I prefer using a 24 hour clock myself. It looks cleaner that way.

anthony



Robinson, Eric wrote:
>> Also, what are the thoughts of having the configuration option
>> be exclusive instead
>
> Inclusive or exclusive works equally well for me. It'll be a few days
> before I can upgrade my ldirectord to the current version and start
> testing...
>
> --
> Eric Robinson
>
>
>
>
> Disclaimer - November 11, 2009
> This email and any files transmitted with it are confidential and intended solely for LinuxVirtualServer.org users mailing list.. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management and Physician's Managed Care. Warning: Although Physician Select Management and Physician's Managed Care have taken reasonable precautions to ensure no viruses are present in this email, the companies cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
> This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
>
> _______________________________________________
> Please read the documentation before posting - it's available at:
> http://www.linuxvirtualserver.org/
>
> LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
> Send requests to lvs-users-request [at] LinuxVirtualServer
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


eric.robinson at psmnv

Nov 11, 2009, 5:37 PM

Post #6 of 7 (871 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

> Reading through the documentation for Time::Period again
> I think the best way to cover the 24 hour period is
> probably to just use hr {0-23}

That sounds perfect.

--
Eric Robinson


Disclaimer - November 11, 2009
This email and any files transmitted with it are confidential and intended solely for LinuxVirtualServer.org users mailing list.. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management and Physician's Managed Care. Warning: Although Physician Select Management and Physician's Managed Care have taken reasonable precautions to ensure no viruses are present in this email, the companies cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users


horms at verge

Nov 25, 2009, 4:59 PM

Post #7 of 7 (682 views)
Permalink
Re: [lvs-users] emailalertperiod configuration option [In reply to]

On Wed, Nov 11, 2009 at 05:37:22PM -0800, Robinson, Eric wrote:
> > Reading through the documentation for Time::Period again
> > I think the best way to cover the 24 hour period is
> > probably to just use hr {0-23}
>
> That sounds perfect.

Looks good to me too.

Anthony, do you want to roll a fresh patch with '{0-23}'?


_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

Linux Virtual Server users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.