|
|
| Author |
Message |
| 25 new of 162 responses total. |
aruba
|
|
response 12 of 162:
| 
Jul 14 05:56 UTC 1999 |
The dialins are working for me, but they're taking four rings to pick up
instead of the usual 1. No doubt this is playing havoc with some people's
scripts which have short timeout periods.
|
i
|
|
response 13 of 162:
|
Jul 14 10:24 UTC 1999 |
I'm seeing extra rings at -3000, but only one further up the trunk hunt.
My guess is that one of the modems isn't answering.
|
scott
|
|
response 14 of 162:
|
Jul 14 11:02 UTC 1999 |
I'll have to check out -3000, I guess. But the phone system does forward
after 3 rings to the next line, so no big problem.
|
senna
|
|
response 15 of 162:
|
Jul 14 14:36 UTC 1999 |
Took me three tries to get backtalk to start reading agora, which
started with this item.
|
richard
|
|
response 16 of 162:
|
Jul 14 21:10 UTC 1999 |
how come picospan seems to cut off one-line responses? often, when
someone does a one line response, picospan skips the text, and I have to
pull the item up in backtalk to read it
|
scott
|
|
response 17 of 162:
|
Jul 14 21:11 UTC 1999 |
That's usually a settings issue on your terminal.
(epadding to make more than one line)
|
tpryan
|
|
response 18 of 162:
|
Jul 14 21:52 UTC 1999 |
It just took four rings to get the terminal server to answer the phone.
|
scott
|
|
response 19 of 162:
|
Jul 14 22:46 UTC 1999 |
Yes, 761-3000 is not answering so it bumps up the hunt after 3 rings. I'm
going to be dropping by the Pumpkin this evening to check it out.
|
lowclass
|
|
response 20 of 162:
|
Jul 15 13:51 UTC 1999 |
As of 9:40 am, the 761-3000 modem seemed to pick up quickly.
(course this early in the morning, I might have dosed off between
rings..)
|
drew
|
|
response 21 of 162:
|
Jul 19 18:12 UTC 1999 |
On logging in, the message "Vfork failed" appeared. What does this mean?
|
mcnally
|
|
response 22 of 162:
|
Jul 19 18:43 UTC 1999 |
It means that the system vfork() call failed and whatever was trying to
do it reported the error to you.
vfork is one of a family of system calls that create new processes --
for example the system login program creates a shell process for you
when you log in. the most common reason why vfork might fail is if
the system is "out" of processes (simultaneous running processes are a
finite resource on Unix systems, you can only have so many at once.)
usually this occurs when either (a) some jerk is running a "fork bomb"
to deliberately use up processes, or (b) when the system has been
running for a very long time and processes have "leaked" for some
reason (i.e. processes that end for some reason haven't been returned
to the pool of free process ids available and eventually they all get
used up..) usually a reboot is needed to fix problem (b).
|
drew
|
|
response 23 of 162:
|
Jul 20 20:55 UTC 1999 |
The system did continue to function normally after that, so both (a) and (b)
seem implausible. Maybe there was just unusually heavy traffic at that time?
|
arund
|
|
response 24 of 162:
|
Jul 28 12:34 UTC 1999 |
pass.
|
nestene
|
|
response 25 of 162:
|
Jul 29 09:36 UTC 1999 |
I've been having trouble trying to dial in on 761-3000 these last few weeks.
Usually, things hang after I'm told it might take a few seconds to connect,
but today I didn't get anything after my modem's CONNECT notice. As usual,
dialing in on 761-3411 worked perfectly.
|
e4808mc
|
|
response 26 of 162:
|
Jul 29 14:29 UTC 1999 |
Same problem this morning. 3000 hangs there without giving me the few seconds
to connect notice.
|
scott
|
|
response 27 of 162:
|
Jul 29 16:05 UTC 1999 |
I think we may have a futzy terminal server port.
|
aruba
|
|
response 28 of 162:
|
Jul 29 16:42 UTC 1999 |
I couldn't get in on 3000 or 5041 today.
|
krj
|
|
response 29 of 162:
|
Jul 29 17:46 UTC 1999 |
I can't get 761-3000 to work today.
Last night, in party, dea said that he had to hunt around a bit to find
a working phone line on Grex.
|
keesan
|
|
response 30 of 162:
|
Jul 29 19:48 UTC 1999 |
Same problem yesterday and today. We thought it was in the computer, tried
three different modems, two com ports, a new version of Procomm, and then
another computer. Glad to know it is not at our end.
|
scott
|
|
response 31 of 162:
|
Jul 29 22:01 UTC 1999 |
I dinked around with the terminal zerver this afternonn, but couldn't find
anything really wrong. I power-cycled a few modems and left it for now. I
dial in enough to notice any problems...
|
tpryan
|
|
response 32 of 162:
|
Jul 29 22:09 UTC 1999 |
Problem persists. And I thought you where practiceing shutting down
early.
|
scott
|
|
response 33 of 162:
|
Jul 29 22:25 UTC 1999 |
Ah well. back to the salt mines...
|
krj
|
|
response 34 of 162:
|
Jul 29 23:19 UTC 1999 |
I was not able to get in on 761-3000 just now, but 761-5041 got me in.
|
mooncat
|
|
response 35 of 162:
|
Jul 30 01:57 UTC 1999 |
Took me several tries at 761-3000, but eventually it worked.
|
aruba
|
|
response 36 of 162:
|
Jul 30 06:25 UTC 1999 |
I couldn't get in on 300 or 5041 tonight, but 3411 worked. So I'm betting
it's the 5041 port that has a problem.
|
