|
Grex > Coop6 > #106: Why does it take so Long to Get into Grex? | |
|
| Author |
Message |
| 18 new of 42 responses total. |
sidhe
|
|
response 25 of 42:
| 
Feb 21 05:47 UTC 1995 |
Well, all I know is that tonight it took all of ten minutes to
get from connection, to picospan prompt. <sigh> I just wish, sometimes,
that there was some way to stay 8ahead* of the game, instead of
fighting problems only when they really flare up..
But, what are you, psychic? Oh, well..
|
carson
|
|
response 26 of 42:
|
Feb 21 06:12 UTC 1995 |
ya know what, sidhe? The name server thingy finally went down.
*That's* why it took so long for you to log in.
|
carson
|
|
response 27 of 42:
|
Feb 21 06:15 UTC 1995 |
sidhe ttyqf 198.111.64.10 Mon Feb 20 23:50 still logged in
|
steve
|
|
response 28 of 42:
|
Feb 21 06:36 UTC 1995 |
It's interesting to note that the load average on Grex has been elevated
these last several days. Greg and I were talking about this tonight, and
when we looked at the system we didn't see anyting out of the ordinary. It
is possible that we're seeing a operating system problem, such that once
Grex has been up for a long time (well, not long, but long enough), memory
starts getting 'fragmented' and things slow down because of this. We've
heard of problems with SunOS 4.1 for a SPARC, but perhaps the problem
carries over across to this platform (68020). So Grex will get rebooted
tomorrow, and I think we'll try to reboot it every other day for a few
just to see what happens.
|
carson
|
|
response 29 of 42:
|
Feb 21 06:37 UTC 1995 |
That's right... Grex has been up for over four days now...
|
sidhe
|
|
response 30 of 42:
|
Feb 21 15:35 UTC 1995 |
So maybe you guys are psychic.. Who knew?
|
jep
|
|
response 31 of 42:
|
Feb 25 07:40 UTC 1995 |
YAPP comes with source for $100, yes.
This may not be the time to discuss M-Net and Picospan and the 486,
but Marcus, MSEN already had a copy of Picospan running on a 486 when
M-Net was in such a hurry to get a copy. We were saved by YAPP (and I was
told by someone else that your knowledge of YAPP availability was one
reason we couldn't get Picospan when we needed it, or for 4 months after
we moved to the 486). (The *only* information Arbornet ever got on it's
long-delayed order -- finally cancelled -- was third or fourth hand.)
|
mdw
|
|
response 32 of 42:
|
Feb 26 04:28 UTC 1995 |
( You're right - it isn't - and rumours can be so dangerous. )
|
jep
|
|
response 33 of 42:
|
Feb 27 02:44 UTC 1995 |
(Sorry, just old frustration talking.)
|
nephi
|
|
response 34 of 42:
|
Mar 2 07:17 UTC 1995 |
I really prefer PicoSpan over YAPP. On several occasions, while using
YAPP on M-net, I have encountered bugs (like being called FW of a conference
and not being able to enter that conference, etc.) I've never encountered
a bug with PicoSpan.
|
tsty
|
|
response 35 of 42:
|
Mar 3 08:52 UTC 1995 |
mdw has hidden those features verrrrrrrry well ... <g>
|
ajax
|
|
response 36 of 42:
|
Mar 3 16:26 UTC 1995 |
Indeed, PicoSpan is very stable. I haven't personally had any problems
with YAPP either, but I'd definitely want to check with other longtime
users to get their impressions, if Grex plans to switch. By the way,
is could Grex license PicoSpan source code?
|
jep
|
|
response 37 of 42:
|
Mar 3 17:01 UTC 1995 |
I rarely notice the differences between YAPP and Picospan. YAPP has
some nice features Picospan doesn't (the participants file is stored in
the ulist for each conference, which makes it speedy enough to use; YAPP
can handle Usenet News groups as conferences and can have shared
conferences via e-mail) but these are little things for most users. M-Net
users complain about losing their participation files for the general
conference if they're disconnected before they exit the conference. I
don't hear about that much on Grex. (I've had this problem once in the
last year on M-Net.) YAPP has the capability of "fishbowl" conferences;
conferences in which only the people on the ulist can enter items, but
everyone can read them. We use this for a couple of administrative
conferences.
Really, it doesn't matter too much to me whether I'm using YAPP or
Picospan.
|
nephi
|
|
response 38 of 42:
|
Mar 3 21:06 UTC 1995 |
Gee, those sound like some pretty neat features.
|
ajax
|
|
response 39 of 42:
|
Mar 6 16:24 UTC 1995 |
Re #37, coincidentally, I lost my agora participation file on Grex
once last year...it's bumming with a big conference! I think it was
due to disk fullness. If so, it seems like both PS and YAPP might
benefit by writing a new participation file before deleting the old
one, then doing a file rename...though that's a tradeoff between speed
and reliability.
|
lilmo
|
|
response 40 of 42:
|
Mar 6 22:11 UTC 1995 |
Well, we can either rename, write, delete; or delete, write. I don'
think that there's much of a speed sacrifice with the more reliable
former method.
|
ajax
|
|
response 41 of 42:
|
Mar 7 00:07 UTC 1995 |
Nope, I wouldn't think so either. But depending on the O/S, rewriting
an existing file is usually faster than creating a new file, as it saves
having to allocate a new beginning file block, and having to store a
reference to the new file's name and location (already done with an
existing file you'd rewrite). I could see it taking the better part of
a second with a clunky drive, but I dunno for sure.
|
lilmo
|
|
response 42 of 42:
|
Mar 7 21:14 UTC 1995 |
Ahhh.... I hadn't thought about it that way... Now I see why
it might be slower by more than an insignificant amount. Thanks
for the explanation.
|