|
|
| Author |
Message |
| 25 new of 274 responses total. |
valerie
|
|
response 150 of 274:
| 
Jan 24 16:37 UTC 1997 |
This response has been erased.
|
albaugh
|
|
response 151 of 274:
|
Jan 24 19:17 UTC 1997 |
Meanwhile, performance is *dog*-*meat*. :-(
|
dang
|
|
response 152 of 274:
|
Jan 24 23:41 UTC 1997 |
Happened to me too. (Getting frozen and kicked off.) Actually, one time, the
reboot time was short enough that my connection didn't time out, and I picked
up right where I left off. There are plans for a new gryps. How are they
coming?
|
dpc
|
|
response 153 of 274:
|
Jan 25 02:05 UTC 1997 |
Do we want to know what "gryps" is and what's gripping it?
|
richard
|
|
response 154 of 274:
|
Jan 25 02:09 UTC 1997 |
GRYPS = GREX REPEATEDLY YAWNING PRETTY STEADILY
|
drew
|
|
response 155 of 274:
|
Jan 25 03:19 UTC 1997 |
Re #148:
That is exactly what I mean; the means whereby I read the conferences from
work. I *think* the mail handler is executing - the header to the script
appears in the inmail.emc file - but the output never makes it back to my
workstation. This is a fairly recent problem.
|
scg
|
|
response 156 of 274:
|
Jan 25 09:00 UTC 1997 |
I have everything to put together the new gryps except a working hard drive.
I haven't had time to look for one yet.
|
srw
|
|
response 157 of 274:
|
Jan 26 01:06 UTC 1997 |
We're all pretty confident that a newer version of gryps's OS would eliminate
a large amount of this flakiness. We won't be sure until it has been upgraded.
|
scg
|
|
response 158 of 274:
|
Jan 26 05:45 UTC 1997 |
Actually, I'm not at all confident of that. We keep hearing about FreeBSD
routers that stay up for months at a time. Indeed, I've got a router at work
running Linux (theoretically less stable) that has been problem free. The
thing that worries me, though, is that I've never heard of a situation where
a FreeBSD router has been pushed as hard as we push gryps. Most routers have
the very easy task of taking packets in one interface and shoving them out
the other. Gryps, on the other hand, is funneling packets from an extremely
active ethernet through what it is probably safe to say is one of the world's
most congested 28.8K modem links. What this means is that rather than just
pushing packets it gets out the other interface, gryps has to queue the
packets often for as much as fifteen seconds before it can fit them through
the link, all the while being bombarded with more and more stuff.
Will a newer version of FreeBSD be more stable? It might, but I won't hold
my breath. The only way to know is to try it.
|
valerie
|
|
response 159 of 274:
|
Jan 26 19:57 UTC 1997 |
This response has been erased.
|
scg
|
|
response 160 of 274:
|
Jan 26 20:37 UTC 1997 |
I've managed to do weird things to PPP and crash FreeBSD 2.1.0, two versions
after what we're running.
|
valerie
|
|
response 161 of 274:
|
Jan 26 21:50 UTC 1997 |
This response has been erased.
|
kentn
|
|
response 162 of 274:
|
Jan 26 23:11 UTC 1997 |
I did not find 2.1.5 all that stable just for mild home use, but 2.1.6
seems better in terms of stability for that purpose. Neither can match my
experience with 2.0, though (to be fair, my system hardware configuration
has changed since I ran 2.0 and that might have impacted stability).
FreeBSD 2.2R (the last of the 2.x development, I believe) is due out
real soon, and 3.0 is coming along. One can only hope that they will
become more bulletproof, but that remains to be seen.
Have staff tried contacting Jordan Hubbard, et al. regarding the use of
fbsd in this extremely hard usage situation?
|
tsty
|
|
response 163 of 274:
|
Jan 27 05:30 UTC 1997 |
ummmmm, as a question, would a simpler os than freebsd do gryps any good? and
also more stable albeit older but rewritten for the newest processors as
well as the 286+ level.
|
valerie
|
|
response 164 of 274:
|
Jan 27 08:01 UTC 1997 |
This response has been erased.
|
davel
|
|
response 165 of 274:
|
Jan 27 11:21 UTC 1997 |
Re 159: Um, Valerie, "completely rewritten" means "introduced a whole lot of
brand new bugs".
|
ryan1
|
|
response 166 of 274:
|
Jan 27 16:06 UTC 1997 |
This morning, Grex's load average was skyrocketing up into the 20's and
30's. Also, at one point Grex lost it's internet connection for a few
minutes (I suspect the router may have rebooted.) After Grex regained
it's internet connection, the load average went down under 8.
|
kentn
|
|
response 167 of 274:
|
Jan 27 23:56 UTC 1997 |
A number of the FreeBSD developers hang out every day on the Usenet
group comp.unix.bsd.freebsd.misc, including Jordan (the Pres. of FBSD, Inc.).
More of the in-depth internals type of hacking information can be had
by joining the appropriate FreeBSD mail list, of which there are several
(see the fbsd web page, www.freebsd.org). From what I've seen, they
are very willing to help a knowlegeable sysadmin with specific problems.
There is also an archive of mail list activity that can be searched for
bug reports & fixes/patches/work-arounds.
|
richard
|
|
response 168 of 274:
|
Jan 28 01:08 UTC 1997 |
Grex is REALLY slow on the 'net. For the olast couple of days, it has
actually been faster to use backtalk than picospan! When I'm on picospan,
it feels like I'm on a ten year old 300 baud modem.
Is this hardware related? Is anything still swapped out?
|
valerie
|
|
response 169 of 274:
|
Jan 28 14:21 UTC 1997 |
This response has been erased.
|
richard
|
|
response 170 of 274:
|
Jan 28 18:49 UTC 1997 |
Interesting...I was entering an item in agora via picospan and grex froze. I
still have that edit screen up and its still frozen. I'm typing this via
backtalk which is responding. Very weird.
|
richard
|
|
response 171 of 274:
|
Jan 28 18:50 UTC 1997 |
Interesting...I was entering an item in agora via picospan and grex froze. I
still have that edit screen up and its still frozen. I'm typing this via
backtalk which is responding. Very weird.
|
davel
|
|
response 172 of 274:
|
Jan 28 19:42 UTC 1997 |
Richard, you're repeating yourself again.
|
davel
|
|
response 173 of 274:
|
Jan 28 19:48 UTC 1997 |
Got a help request from qt314. She says when she runs bbs she gets the
following message, after which it comes up but acts weird:
stty: standard input: operation not supported on socket
She says this is only since last night, and that she's dialed in,
which makes me wonder what socket is involved.
I told her to email staff, since I'm no help on this one, but thought
I'd post it here. My *only* thought was that her shell is tcsh.
I've only been half-reading the discussion of linking it with lshadow,
since I don't use it myself; is the new version still in another name,
or is that what she's running? If the latter, I'd say that's likely
the cause, just on the basis of post-hoc-ergo-propter-hoc, but of
course that's shaky logic. Anyway, y'all, here's a big bunch of nothing.
|
ajax
|
|
response 174 of 274:
|
Jan 29 01:03 UTC 1997 |
I got an unusual picospan message earlier today. Looks like it fixed
its own problem, but I'll post it anyway:
>Respond or pass?
>(Fixed item 40 flags 3c->1c mtime 32ee0551)
>(Fixed item 40 rcnt 65)
>
>Item 40: Clinton v. Paula Jones
>Entered by Mary Remmers (mary) on Sun, Jan 19, 1997 (09:02):
>
>7 new of 64 responses total.
>
>.
>.
>.
|
