|
Grex > Coop7 > #47: A question on bringing the system back up after it's been off the net | |
|
| Author |
Message |
| 15 new of 39 responses total. |
davel
|
|
response 25 of 39:
| 
May 31 00:59 UTC 1995 |
There have in the past been complaints from those who pay toll charges to AA
about modems which connect when Grex isn't up.
|
steve
|
|
response 26 of 39:
|
May 31 01:17 UTC 1995 |
Thats a different problem, and can only be solved by more of the
BSR "light controllers" that control gryps and its modem right now.
That can be done however, and should be, down after the long list of
more pressing things.
|
adbarr
|
|
response 27 of 39:
|
May 31 01:44 UTC 1995 |
Steve - - next time we meet - explain 26 please. Thanks.
|
davel
|
|
response 28 of 39:
|
May 31 11:06 UTC 1995 |
He means that modems can be powered on & off remotely, with current
technology, but that it's fairly low priority.
STeve, I was too brief. There is the separate issue you mention. But
you propose deliberately leaving Grex immune to logins, but with its
modems connecting, for an extended period; so some may complain.
Possibly not - after all, if the connection also delivers accurate
information on when Grex will again be available, that may outweigh
the cost of one extra call.
|
lilmo
|
|
response 29 of 39:
|
Jun 21 20:42 UTC 1995 |
Before concluding that davel's last statement is true or false, perhaps we
should ask those to whom it applies...
|
davel
|
|
response 30 of 39:
|
Jun 21 21:57 UTC 1995 |
I don't remember who it was. I remember some fairly strongly-worded
comments being posted when Grex was answering-but-not-up for hours or
days at a time fairly frequently for a while. I'm raising the issue,
not giving an answer. My own call would indeed be that this is indeed
a good thing to do.
|
scg
|
|
response 31 of 39:
|
Jun 21 22:56 UTC 1995 |
I think that was Jared, Complaining about the $.06 per call charge for every
call over 400 per month. I'm surprized that $.06 bothered him, and I really
can't imagine it bothering too many other people.
|
robh
|
|
response 32 of 39:
|
Jun 21 23:13 UTC 1995 |
Back in the days when I called boards other than Grex >8) I made
well over 400 calls a month. They do add up, trust me.
|
davel
|
|
response 33 of 39:
|
Jun 22 09:59 UTC 1995 |
Jared may have been one. At least one person was making long distance
calls (Saline? Belleville?). That's more what I would worry about.
|
popcorn
|
|
response 34 of 39:
|
Jun 22 12:14 UTC 1995 |
Ja, I thought it was someone who was making long-distance calls into Grex.
(md? sarrica? dunno.)
|
davel
|
|
response 35 of 39:
|
Jun 22 22:00 UTC 1995 |
Aha! <ding ding ding> md is the person I was remembering most distinctly,
I think.
|
lilmo
|
|
response 36 of 39:
|
Aug 22 06:17 UTC 1995 |
So.... let us attempt to obtain the opinion(s) of one or more of these ppl.
|
arthurp
|
|
response 37 of 39:
|
Jan 13 06:30 UTC 1996 |
Couldn't the nologins thing be automated. As someone sits at the
console rebooting. They could run a script with a timing paramter.
The script could sleep for a time based on downtime, and then wake
up and delete the nologins flag. Disabling logins *does* just
consist of the presence of a file in /etc, doesn't it?
|
steve
|
|
response 38 of 39:
|
Jan 14 06:15 UTC 1996 |
Yes, quite right. We could indeed automate it, and I've thought
about that some. It's one of those "nice" things to have around.
...It could also mutate into more work too. When I've done this in
the past, it was to keep net users off, but I also wound up keeping
local users off the dialins at this point too, which was an unforunate
side effect of this.
Ideally, we should have a way to keep either sets of people off
the system, local or net users.
|
srw
|
|
response 39 of 39:
|
Jan 14 07:17 UTC 1996 |
That requires some code in .login which we were thinking we'd need to be
doing whhen the terminal server is introduced, anyway.
|