|
|
| Author |
Message |
| 25 new of 205 responses total. |
scott
|
|
response 25 of 205:
| 
Jun 23 20:59 UTC 2000 |
Hmm? Sorry, didn't quite catch what you said, willard. Sounded something
like "M-Net would never be down this long".... (big toothy grin)
(Way back there with cmcgee's request for advance notice on stuff like this:
Well, we can't really give notice in this sort of thing. Moments after we
came back on the net we were being bombarded with mail, so it's not like we
could leave logins open for a few hours so people could find out the status.
And staying off the net longer would be bad)
|
cmcgee
|
|
response 26 of 205:
|
Jun 24 00:40 UTC 2000 |
Ah, more wisdom. Thank you.
|
albaugh
|
|
response 27 of 205:
|
Jun 24 03:52 UTC 2000 |
Can grex establish a small web site somewhere (e.g.
www.yahoo.com/~grex) for the express and only purpose of indicating the
system status of grex (e.g. "up", "down because...", etc.)? When the
net connection is down, only dialing in (for those who can) holds any
chance to discover that fact. And grex could be entirely down, with
therefore no way to inform people of the particulars.
|
gelinas
|
|
response 28 of 205:
|
Jun 24 03:53 UTC 2000 |
I used ping and traceroute to determine that grex was down and why.
|
albaugh
|
|
response 29 of 205:
|
Jun 24 04:14 UTC 2000 |
Re: #28: That sounds like you had access to another system from which
you could execute UNIX commands on the internet. I'm sure many people
don't have that capability - I don't.
|
jmsaul
|
|
response 30 of 205:
|
Jun 24 04:18 UTC 2000 |
I doubt he was suggesting it as a general alternative to your website idea
-- which is a good one. I'm very glad that we weren't serving M-Net's website
from the M-B0x at the time of the crash.
|
gelinas
|
|
response 31 of 205:
|
Jun 24 04:54 UTC 2000 |
Actually, I think it is a general solution, for those who care. Windows now
ships with tracert, and WhatRoute is available for the Macintosh.
Of course, that is no reason not to put up a web site, as long as there
is a volunteer or three to maintain it.
|
richard
|
|
response 32 of 205:
|
Jun 24 06:54 UTC 2000 |
much thanks to grex's staff folks for resolving grex's isdn issues and
getting grex safely back on the 'net.
grex lives.
|
remmers
|
|
response 33 of 205:
|
Jun 24 12:53 UTC 2000 |
Thank you, Richard. I think STeve, Scott, and especially Jared
Mauch (not staff, but a good friend of Grex) did most of the work.
If we established an "offsite website" for reporting system status,
can someone think of a good way for people to find it when Grex
itself is inaccessible? They'd have to remember the URL, or have
had the foresight to bookmark it.
|
kaplan
|
|
response 34 of 205:
|
Jun 24 13:21 UTC 2000 |
Wasn't there a web page on http://hvcn.org where one could go to get
info about grex when grex was down?
|
remmers
|
|
response 35 of 205:
|
Jun 24 13:53 UTC 2000 |
I don't remember that, but it's certainly plausible. If it's
true, I think it illustrates one of the problems with the concept.
|
scott
|
|
response 36 of 205:
|
Jun 24 13:55 UTC 2000 |
We will still need to take Grex offline to reassign IP addresses and fix all
the the things that break when we change IP addresses.
|
tpryan
|
|
response 37 of 205:
|
Jun 24 14:19 UTC 2000 |
It is hard to tell the difference when the telephone server
grypos, is deliberatly hanging up the phone (such as during the
e-mail rush) and it's normal random hang ups after connection.
|
senna
|
|
response 38 of 205:
|
Jun 24 15:04 UTC 2000 |
Wouldn't have to be much of a site, really. Just a line or two stating grex's
status, and a link to grex for when it's up.
|
remmers
|
|
response 39 of 205:
|
Jun 24 17:24 UTC 2000 |
Right. But if kaplan is correct and there already is such a site,
ease of maintenance is not the issue.
|
danr
|
|
response 40 of 205:
|
Jun 24 18:14 UTC 2000 |
It would be if no one has the proper access to update it. :)
If there isn't such a page on hvcn.org, I'd be happy to put up a page on one of
my websites.
|
kaplan
|
|
response 41 of 205:
|
Jun 24 18:32 UTC 2000 |
See http://www.hvcn.org/info/grex/status.html
Also see HVCN's communitynet conference item 5. (I seem to have
forgotten how to construct a short url that lets anyone read an item
via Backtalk. It includes the word "peek", right?)
|
aruba
|
|
response 42 of 205:
|
Jun 24 20:49 UTC 2000 |
To see this response, I'd give the URL
/------------------------------------------------------\
| http://www.cyberspace.org/cgi-bin/bt/peek:agora,4,42 |
\------------------------------------------------------/
|
albaugh
|
|
response 43 of 205:
|
Jun 24 22:20 UTC 2000 |
OK, can we count on the URL in #41 to be reliable and the one people should
go to, to find out about grex status? If so, let's talk it up, and get people
with web browsers to bookmark it, and put it next to their bookmark for grex.
Grex should include the URL somewhere prominently in its "greeting" pages,
and in the FAQ.
|
scg
|
|
response 44 of 205:
|
Jun 25 07:22 UTC 2000 |
Before you change IP addresses, some DNS stuff needs to get changed at the
NIC and at my former employer. I should probably be the one to deal with
that, but it's been on my to do list for a while.
I don't have a computer at the moment. I'm living in a hotel that has a
couple of Net connected computers in the lobby, so I have a little bit of Net
access. My mail server is also down at the moment, so I don't have access
to e-mail (hopefully, some nice person in Michigan will fix that situation
for me). I'm also supposed to be looking for a place to live, and starting
my new job on Monday (at which point I should have more Net access but less
free time). Hopefully I'll be able to be useful to Grex sometime in the near
future.
Thanks, everybody, for dealing with this. It sounds like I picked an
interesting week to be doing my cross country road trip and not touch a
computer.
I'd also like to second what was said about not bugging staff people on the
phone. I got woken up at some really early hour of the morning by somebody
who would only identify himself as "Dave," who called my cell phone to tell
me that Grex was down, and seemed rather indignant when I told him that I
didn't appreciate being woken up, knew nothing about the problem, and had no
intention of doing anything about it.
|
remmers
|
|
response 45 of 205:
|
Jun 25 14:03 UTC 2000 |
Re #43: Kevin - I'd suggest emailing webmaster@cyberspace.org with
your suggestions.
Who has update access to the offsite status page? I wouldn't have known
how to update it even if I'd remembered that it existed.
Before publicizing the current URL, we might want to give some thought
to making one that's easier to remember. Would it be feasible to make
an address such as "status.cyberspace.org" point offsite?
|
danr
|
|
response 46 of 205:
|
Jun 25 15:48 UTC 2000 |
I have access to that page, and would be happy to update it should anyone want
to send me the info.
|
jared
|
|
response 47 of 205:
|
Jun 25 16:28 UTC 2000 |
I can host a status.cyberspace.org, and provide access
to all staff folks to update it, and provide offsite accounts
for all grex staff to use to converse during such outages.
|
remmers
|
|
response 48 of 205:
|
Jun 25 16:37 UTC 2000 |
That sounds terrific! Thanks, Jared.
I think an easy-to-remember URL that's in the cyberspace.org domain
is much preferable to the current one.
|
remmers
|
|
response 49 of 205:
|
Jun 25 16:41 UTC 2000 |
(It'd be nice for it to have the alias status.grex.org as well.)
|
