I have to agree with Dwight as I have had direct experience from both sides
(customer and tech) with similar issues. Once was from a line that got
pulled slightly loose doing some repair work (took close to 11 hours from
when it happened to the customer calling and complaining to when a couple
of us went back out to resolve the issue to actually having the customer
back up and running) and once was from when a tech at the telco/ISP tripped
over a pile of wiring that was temp uplinking (passfeed) to another rack
when they were doing hardware moves. The unexpected disconnection due to
his tripping and yanking out/breaking hardware, sent a block of almost 200
subscribers S.O.L. for about 27 hours before it was restored (as the
telco/ISP at that point decided: f*** it- it's down, might as well finish
doing the move the way we wanted to anyhow). Also had a few occurrences of
the telco/ISP doing the "whoops" when making changes for someone else in
the field and a few "um, no, uh, it can't be us" issues when they have a
brilliant engineer decide to do a IOS/Firmware/OS, etc upgrade to a router
bank in the early morning hours... unannounced and downing the network for
the customer for several days while trying to fix it.
There are no ass-nazi penguin hippies hanging out with grey/green aliens
with huge anal-probes looking to get you because you are so unique. Put the
lube away, take some nummy chocolate-coated valium and relax, seriously.
...Oh, and watch out for that 12 legged flying monkey on your right (grin).
-John Boffemmyer IV
At 08:42 PM 3/8/2005, you wrote:
From: msokolov
at
ivan.harhan.org
Jay West <jwest at classiccmp.org> wrote:
In case no one caught my previous post on this, a
few days ago I moved =
the queue retention time back up to a reasonable value.
Thank you!
I suspect Michael Sokolov is testing this out for
me, his name servers =
(and thus email) have been down a few hours.
Do you really think that I, after having earned the trust of my circle of
friends (who all have accounts on my various servers, and use and depend on
various services hosted at my data centre) as a competent, reliable and
trustworthy professional system and network administrator for our Circle,
would deliberately shut it down, screwing all our users?! There must be
something seriously wrong with your thinking if you indeed thought so.
Lighten up. Jay was just kidding.
---snip---
DSLAM and the CPE to sync up. So the problem
detected by TDR, which they
dispatched a local telco tech to fix, was NOT an open, but something else.
I very strongly suspect foul play.
---snip---
Wow, you are paranoid. It was more likely that some other
tech ( while trying to find another clean line to fix
a complain about noise ) accidentally bent a wire to cross
your line at one of the junction boxes. This kind of thing
happens regularly ( about every 6 months or so ) to my home
line because I live in an area with a lot of noisy line ( water
in cable ).
Why does everything that happens need to be a conspiracy.
Clumsy techs are much more common than sneaky people. If someone
was actually doing what you suggest, they would most likely have
done a better job. If it wasn't working for you, it most likely
wasn't working for them either.
Dwight
----------------------------------------
Founder, Network Engineer, Tech Analyst
and Web Designer Boff-Net Technologies
http://boff-net.dhs.org/index.html
----------------------------------------