Subj : this echo
To   : Eddy Thilleman
From : Mike Luther
Date : Sun Oct 21 2001 12:08 am

Eddy ..

ml> dagum first message in the area pointer bug 
ml> <<sigh>> if i had seen the
ml> indication that there was a message in here, i'd have answered ml> 
sooner...

 ET> At least your message got out, I don't know why David didn't see it.

As I have tried to explain in the LAN version of all this, it may have to do 
with Steve Loupe's 106/1 in Houston.  Two things went badly wrong in Houston of 
late which have *NOTHING* to do with Steve's capability or service efforts.

    1.) Houston took a substantial environmental whambo with Mother Nature
        and the weather.  Phone line service was bloto to a lot of places
        between those people who depend on Steve, as well as Steve's
        phone line connections as well.

    2.) More or less in the middle of all this, Steve was 'forced' to
        switch his IP feed source.  As he carefully announced, the
        instructions on how to prepare for that and his intentions as
        to un-interrupted service were very explicit.

        The IP swap game went sour.  Many of us who depend on him,
        including me, had no connections with him for more and a day
        or so.  It appeared that a ton of traffic that was bound from
        him to me stacked up at his site, but I can't be sure all of it
        is what there is.  There is some that was here which I am almost
        sure did *NOT* make it through that HUB.  Included in the missing
        stuff was stuff that I'm absolutely sure got missed in R19SYSOP,
        from what we determined later - which is part of what I stand on
        to make this claim.

My post in this area for the help request for APACHE was, it seems, lost in 
this shuffle in Houston, and Dave .. plus I know not whom else, never saw it 
here.  However, as you can see, the link game, in general, for this echo is not 
broken.

Had my Apache help request gone through, and even the answers that it has 
gotten so far, once cross posted to the OS2LAN echo and seen, my bet is that 
this echo would have enough traffic in it to be still traffic validated, but 
barely.  Further, when I get the time do act on what suggestions have been 
posted on my Apache problem, including what Dave himself suggested, I intend to 
re-visit that whole tning.

In specific ..

     ECHO SPECIFIC HERE .. I think!

     1.) It is precisely because Apache for OS/2 is installed in a
         generic form with as little fluff to go wrong as possible,
         that it is up for test here.

     2.) I have a fully paid for version of WSeB that came with my
         DEVCON membership that I have not even put up, to pair
         with whatever Port 80 service I might leave up.

     3.) My IP would *LOV* to have me host my own page at my fixed
         address and I could save some $30 a month to do so.

     4.) There is only so much time to fool with any of this stuff
         with what has to be done to feed me and whomever .. giggle.

     5.) I likely will have lots more questions about the other than
         Apache stuff as I mature in this game.

     6.) To separate that from the actual LAN server questions
         I would have normally thought posting all that here would
         have been right square on topic.


Nor will I in any way question what Dave wants to do about all this.

And I do not want to post messages just to keep it alive, if that's not really 
what is wanted.  Nor is this message being posted if it isn't on-topic and 
point specific.

Obviously, since I'm seeing your traffic and mine is now getting out, it's a 
point in my favor as to support for my explanation of what happened here. 
Life's too short to fight over what the minority wants .. grin.

The core issue is that a loss of service at a critical point in a minimal 
traffic echo can produce results which have to be carefully thought about. That 
is exactly what, I suspect, is happening right now.


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001






--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)

.