|
|
| Author |
Message |
| 25 new of 274 responses total. |
richard
|
|
response 175 of 274:
| 
Jan 29 02:20 UTC 1997 |
#170,#171--- Weird...backtalk posted my last post twice.
|
davel
|
|
response 176 of 274:
|
Jan 29 11:30 UTC 1997 |
Re #174: I believe that those messages mean that your participation file
contained information inconsistent with the info in the item itself. The only
times I've seen them in the past have been when it's been necessary for
someone (cfadm or root) to edit an item, say to remove a response (for
example, on an occasion when someone posted twit responses to every single
item in many conferences).
|
janc
|
|
response 177 of 274:
|
Jan 29 18:53 UTC 1997 |
Re #173: The problem qt314 has is the "stty 20" command in her .tcshrc file.
The .tcshrc file is run everytime you start a shell, and shells are used by
many programs, including picospan, to do things like launch pagers. In such
cases, there is no control terminal for the shell, so the "stty" command will
not work. That command should be moved to her .login file, which is executed
only at login time. Terminal sizes need to be set only once per session, not
every time you start up a shell.
Re #174: What is being fixed in those error messages is the conference sum
file, not a participation file. The sum file contains a compact index of
all the items, telling how many responses each one has, and what flags
(retired, linked, etc) are set. By comparing this to your participation file,
Picospan can quickly find new reponses. What Picospan noticed there is that
the actual item didn't agree with the sum file, in that the flags were
different and the number of responses are different. I'm not sure what the
difference between flags 1c and 3c are. When Backtalk creates an item, it
always creates it as 3c and otherwise it just leaves the flags as it found
them, which I've never seen cause any problems, but who knows? Changes in
the number of responses do indicate that possibly the item file got truncated
or editted.
Re #175: In backtalk, after you post a message it goes on to the next page.
If you hit "reload" on that next page, it will repost the message, because
that was part of the previous transaction. Some browsers will ask you if you
want to "repost form data" when you do this.
|
tsty
|
|
response 178 of 274:
|
Jan 30 07:12 UTC 1997 |
as an addendum to #174, i was also getting those same sorts of
messages *as well as* the mkids too small message, if it makes
a difference and/or assists in fixing something.
|
tsty
|
|
response 179 of 274:
|
Jan 30 07:16 UTC 1997 |
oh.... the other os... minux 2.0. remember that minux was the os
the was *not* drenched in Nifty-Tricks, which NiftyTricks' absence
forced the development of linux.
i have the entire source code and a TERRIFIC, thick text to
accompany it that code. the distribution is cdrom.
|
albaugh
|
|
response 180 of 274:
|
Jan 31 01:08 UTC 1997 |
A curious thing happens to me once in awhile: To logout of grex, I enter
"exit" at the Unix shell "$" prompt. (Oh BTW the context I'm referring to
here is telnetting in to grex.) Almost always I'll be given the "grex login:"
prompt, where I'll enter "exit" again, and the connection will be broken.
Every once in awhile, instead of being disconnected, I'll be given *another*
prompt looking like "#login:" on a new line. I enter "exit" a third time,
and the connection *is* broken. This is no big deal, just thought you staff
types might find it interesting...
|
rcurl
|
|
response 181 of 274:
|
Jan 31 05:29 UTC 1997 |
Happens to me too. Sometimes I get another *login after logging in (for
variety?).
|
valerie
|
|
response 182 of 274:
|
Jan 31 15:25 UTC 1997 |
This response has been erased.
|
dpc
|
|
response 183 of 274:
|
Jan 31 22:02 UTC 1997 |
I am now on ttyh3 and am getting the "chopped-up response"
problem I mentioned earlier. When I read an item in a conference,
the higher the number of the response, the more likely it is
that pieces of the response--or even the entire response--are
missing. When I get to the "respond or pass?" prompt, and I
type the number of a relatively high-number response, that response
and the following ones are displayed with high accuracy at first,
and (again) with pieces missing farther down.
This is *definitely* a modem problem, and definitely a
Grex-only problem.
What have we got on ttyh3?
|
kaplan
|
|
response 184 of 274:
|
Jan 31 23:37 UTC 1997 |
FLow control problem? I dial into grex a lot and have never seen this
problem. Of course I'm not dialing in now, so I can't check how I've got it
set. But I'm sure if you change something in your flow control settings in
your terminal program it'll be fine.
|
dpc
|
|
response 185 of 274:
|
Feb 1 17:24 UTC 1997 |
Nope, this is quite recent problem, only happens when I am on Grex,
and I think only happens on ttyh3.
|
valerie
|
|
response 186 of 274:
|
Feb 2 07:48 UTC 1997 |
This response has been erased.
|
dpc
|
|
response 187 of 274:
|
Feb 2 19:35 UTC 1997 |
24 lines, Valerie--as always for the past 3 years, using the same
hardware, software, incantations, etc. 8-)
|
valerie
|
|
response 188 of 274:
|
Feb 3 06:27 UTC 1997 |
This response has been erased.
|
davel
|
|
response 189 of 274:
|
Feb 3 11:44 UTC 1997 |
If it's always on the same tty at Grex, that seems more likely. Have you
checked the stty settings on that line, as opposed to other lines where you
don't see this?
|
richard
|
|
response 190 of 274:
|
Feb 3 21:22 UTC 1997 |
having trouble telnetting this afternoon...grex countdown isa bit slow and
then when the login prompt comes up, I get left hanging at the password prompt
and end up timed out...happened twice...very aggrivatng
|
valerie
|
|
response 191 of 274:
|
Feb 5 13:58 UTC 1997 |
This response has been erased.
|
dpc
|
|
response 192 of 274:
|
Feb 6 22:29 UTC 1997 |
I have just been on ttyh9 and have not had those "response-chopping"
problems. I am convinced h3 has a bad modem.
Thanx for the offer to stop by, Valerie, but I really think
someone should stop by with a new modem for h3. 8-)
|
giry
|
|
response 193 of 274:
|
Feb 7 05:01 UTC 1997 |
I got a strange message while waiting in the que again so i will post it here.
Feb 6 23:42 Feb 6 23:42 2009 -1 29019 192.217.61.3 LOST HEAD
...29
Feb 6 23:42 Feb 6 23:42 2012 -1 29023 192.217.61.2 LOST HEAD
There it is.
|
jshafer
|
|
response 194 of 274:
|
Feb 8 01:19 UTC 1997 |
Backtalk just crashed when I tried to do an item list in the
Archive conference. I saved the results here; let me know if
they will help and I'll e-mail them to you. (Let me know by
e-mail; it may be a few days before I get back into Agora.)
|
valerie
|
|
response 195 of 274:
|
Feb 9 21:10 UTC 1997 |
This response has been erased.
|
ryan1
|
|
response 196 of 274:
|
Feb 9 21:40 UTC 1997 |
I sometimes get the LOST HEAD messages in the queue also.
|
giry
|
|
response 197 of 274:
|
Feb 10 01:24 UTC 1997 |
Will do valerie.
|
richard
|
|
response 198 of 274:
|
Feb 10 02:08 UTC 1997 |
Backtalk problem...I tried to read a particular day's respohses in an item,
as Backtalk allows to do (clicking "all responses since Yesterday"")
I got error 50: Bad Date Format
|
srw
|
|
response 199 of 274:
|
Feb 10 04:54 UTC 1997 |
LOST HEAD comes from the telnet queuing software when it realizes that it has
become confused and corrects itself. Marcus may be interested in those, but
may not be able to get enough information from them alone to figure out why
the "head" of the queue sometimes gets lost and needs to be deposed.
Backtalk seems to be unable to recognize "yesterday" as a date format, despite
suggesting it as a default in the form (pistachio). Looks like a bug.
|
