You are not logged in. Login Now
 0-24   25-49   46-70   71-95   96-120   121-145   146-170   171-195   196-220 
 221-245   246-270   271-295   296-320   321-345   346-370   371-395   396-420   421-445 
 446-470   471-495   496-520   521-545   546-570   571-595   596-620   621-645   646-670 
 671-695   696-720   721-745   746-770   771-795   796-820   821-845   846-870   
 
Author Message
25 new of 870 responses total.
blaise
response 71 of 870: Mark Unseen   Dec 30 17:48 UTC 2004

I had forgotten that you are using csh, where login is a builtin.  Try
"exec /usr/bin/login" -- that should log you off and let someone else
log in.  Note that once they have logged in, they will have to do the
same to let another person log in; if the next person to log in uses
logout/exit, then it will disconnect.
kentn
response 72 of 870: Mark Unseen   Dec 30 18:02 UTC 2004

Putting literal ANSI escape codes in picospan rsep/isep/ishort (via
.cfonce) doesn't work for changing colors in bbs any longer.  All I get
are the raw codes.  My terminal can show colors just fine otherwise. 
cross
response 73 of 870: Mark Unseen   Dec 30 18:14 UTC 2004

This response has been erased.

kentn
response 74 of 870: Mark Unseen   Dec 30 18:17 UTC 2004

I was running 'bbs' however 'ft' exhibits the same behavior.
cross
response 75 of 870: Mark Unseen   Dec 30 18:39 UTC 2004

This response has been erased.

nharmon
response 76 of 870: Mark Unseen   Dec 30 18:40 UTC 2004

Does anyone know what causes pine to create these .pine-debug1 files in my
home directory? They tend to annoy :)
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.
 0-24   25-49   46-70   71-95   96-120   121-145   146-170   171-195   196-220 
 221-245   246-270   271-295   296-320   321-345   346-370   371-395   396-420   421-445 
 446-470   471-495   496-520   521-545   546-570   571-595   596-620   621-645   646-670 
 671-695   696-720   721-745   746-770   771-795   796-820   821-845   846-870   
Response Not Possible: You are Not Logged In
 

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