You are not logged in. Login Now
 0-24   25-49   50-74   52-76   77-101   102-126   127-151   152-176   177-201 
 202-226   227-251   252-276   277-301   302-326   327-351   352-376   377-401   402-426 
 427-451   452-476   477-501   502-526   527-551   552-576   577-601   602-626   627-651 
 652-676   677-701   702-726   727-751   752-776   777-801   802-826   827-851   852-870 
 
Author Message
25 new of 870 responses total.
cross
response 77 of 870: Mark Unseen   Dec 30 18:47 UTC 2004

This response has been erased.

albaugh
response 78 of 870: Mark Unseen   Dec 30 19:53 UTC 2004

When I just went to run mail I got this:


$ mail

/tmp: write failed, user disk limit reached
mail: /tmp: Disc quota exceeded


Wassup with that?!
albaugh
response 79 of 870: Mark Unseen   Dec 30 19:57 UTC 2004

I am seeing the last line of new / newresponse bbs items missing.
I forget what I had set my pager to - more or less - but now instead of seeing
"More" I am seeing "byte xxxx".  What gives?
gull
response 80 of 870: Mark Unseen   Dec 30 20:02 UTC 2004

Missing the last line of items is often a symptom that the number of
rows on your terminal is not the same as the system thinks it is.
albaugh
response 81 of 870: Mark Unseen   Dec 30 20:06 UTC 2004

(I can't read that last line. :-)

If it says something about number of lines per screen in some config file
setting somewhere, then since I didn't change anything, it's something that
got broken during nextgrex'ing.  Should I go on a search and destroy mission
for myself (and if so, where?), or will something systemic be fixed?

blaise
response 82 of 870: Mark Unseen   Dec 30 20:42 UTC 2004

Gull said:
 Missing the last line of items is often a symptom that the number of
 rows on your terminal is not the same as the system thinks it is.

What terminal type are you set to?  (echo $TERM)

This line is for the line-eater (oh, that takes me back...).
cross
response 83 of 870: Mark Unseen   Dec 30 20:56 UTC 2004

This response has been erased.

tod
response 84 of 870: Mark Unseen   Dec 30 21:02 UTC 2004

the !lock_my_terminal and !lock programs are defunct
drew
response 85 of 870: Mark Unseen   Dec 30 21:08 UTC 2004

    Intermittently there occurs some sort of condition where (a) Pine does
not function, and (b) attempts to enter even a single character into a BBS
response result in a "Core dumped" error message. It's not happening now, but
did happen last night and another previous time.
gelinas
response 86 of 870: Mark Unseen   Dec 30 22:16 UTC 2004

I think I fixed kermit.  Try it; if it doesn't work send a message to staff,
please.
keesan
response 87 of 870: Mark Unseen   Dec 30 23:35 UTC 2004

Pine no longer complains about permissions.   In my home director I find no
pine debug files but there are three '0' length pinerc-numbered files (1 of
3, etc) from June 20 which I presume I can delete.  Kermit worked for
telnetting to sdf, thanks Joe.  I will try exec /usr/bin/login (is this
different from /usr/bin/login?) and if it works make an alias.  But ssh worked
okay to change accounts.  
keesan
response 88 of 870: Mark Unseen   Dec 30 23:47 UTC 2004

exec /usr/bin/login, logged in as jdeigert, exit > NO CARRIER.
I don't think I will bother trying without the exec.  ssh works.
There are still two unread 'new items' in homme that cannot be read or
fixseen'ed.  
cross
response 89 of 870: Mark Unseen   Dec 30 23:50 UTC 2004

This response has been erased.

keesan
response 90 of 870: Mark Unseen   Dec 30 23:52 UTC 2004

I cannot fixseen, read, or even 'b n' without getting the messages 'bad item
file header' for 'homme' - will have to actually read the items.
keesan
response 91 of 870: Mark Unseen   Dec 30 23:53 UTC 2004

I forgot I CANNOT read the items so I have no idea  what numbers they are.
Perhaps I can delete something in my home directory if nobody else has the
problem (a conference file).
keesan
response 92 of 870: Mark Unseen   Dec 30 23:56 UTC 2004

I deleted two files starting in .homme which made no difference so the problem
may be elsewhere than my home directory.
keesan
response 93 of 870: Mark Unseen   Dec 31 00:01 UTC 2004

I just went to the homme conference again (after getting that bad item file
header message) and this time it was only 1 brand new item and this time I
could also read it so the problem appears to be local not global and is
fixed.  
gelinas
response 94 of 870: Mark Unseen   Dec 31 00:16 UTC 2004

I noticed that one of the item files in /bbs/homme was owned differently than
the others, so I changed it to match.
keesan
response 95 of 870: Mark Unseen   Dec 31 00:28 UTC 2004

Thanks, Joe, you must have done that before I tried homme again.
Everything is working for me now, how boring.   Grex did hang up on me once
but that is not new.
jep
response 96 of 870: Mark Unseen   Dec 31 04:36 UTC 2004

re resp:2: Yes, nethack is now working great.  Thanks!
albaugh
response 97 of 870: Mark Unseen   Dec 31 06:54 UTC 2004

Hmmm, I may not be seeing a missing last line now.  But anyway, as instructed:

$ echo $TERM
vt100
$ stty -a
speed 9600 baud; 24 rows; 80 columns;

Looks pretty standard to me...
rcurl
response 98 of 870: Mark Unseen   Dec 31 06:56 UTC 2004

I have noticed that login no longer accepts ssh1 (ssh2 now OK - this is
just an observation). 
albaugh
response 99 of 870: Mark Unseen   Dec 31 06:58 UTC 2004

!more .cfonce
# here is where you can put PicoSpan customization
define pager more

And under nextgrex, as I mentioned, my "more" prompt says "byte xxx".

Also note that when I run mail under nextgrex, and do a reply, when I
use ~p to "print" what my reply is going to look like, it doesn't seem
to honor a pager setting as it did under old grex.
twenex
response 100 of 870: Mark Unseen   Dec 31 11:31 UTC 2004

What do you want your "more" prompt to say?

Is the mail problem actually with the program "mail", or another mailreader?


drew
response 101 of 870: Mark Unseen   Dec 31 22:37 UTC 2004

    The problem that I mentioned in Response 85 occurred again last night.
 0-24   25-49   50-74   52-76   77-101   102-126   127-151   152-176   177-201 
 202-226   227-251   252-276   277-301   302-326   327-351   352-376   377-401   402-426 
 427-451   452-476   477-501   502-526   527-551   552-576   577-601   602-626   627-651 
 652-676   677-701   702-726   727-751   752-776   777-801   802-826   827-851   852-870 
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss