You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   105-129   130-154   155-179   180-204 
 205-229   230-254   255-279   280-304   305-329   330-354   355-379   380-404   405-429 
 430-454   455-479   480-504   505-529   530-554   555-579   580-604   605-629   630-654 
 655-679   680-704   705-729   730-754   755-779   780-804   805-829   830-854   855-870 
 
Author Message
25 new of 870 responses total.
rcurl
response 130 of 870: Mark Unseen   Jan 1 20:36 UTC 2005

Could  it have been created because I was reading my mail for the first
time with newPine?
albaugh
response 131 of 870: Mark Unseen   Jan 1 21:00 UTC 2005

I appears that the idle zapper is not working right in the following
situation:

Connected to grex via internet.  Logged in via telnet.
Did "exec login" to another account.  At a certain point the following was
displayed:


Sat Jan  1 13:58:09
This terminal has been idle 15 minutes. If it remains idle
for 5 more minutes it will be logged out by the system.



Logged out by the system.


But no disconnect was performed.  The "Logged out" line was repeated every
so often.  But my sh was still responding, and whoami showed that I was still
the second account.
cross
response 132 of 870: Mark Unseen   Jan 1 22:48 UTC 2005

This response has been erased.

keesan
response 133 of 870: Mark Unseen   Jan 2 01:12 UTC 2005

Why would Jim get the disk quota exceeded message only when he used pine, not
when he logged into his account?
twenex
response 134 of 870: Mark Unseen   Jan 2 01:15 UTC 2005

There are two different quotas for home directory space and mail.
keesan
response 135 of 870: Mark Unseen   Jan 2 01:26 UTC 2005

Yes, and he has about 100K of mail so why get a quota message when using pine?
keesan
response 136 of 870: Mark Unseen   Jan 2 01:32 UTC 2005

I just deleted 8MB of freedos image files from his home directory but that
does not explain why the quota message showed up when going into pine.
When will the new disk quotas be enforced?   I don't know why Jim did not use
sdf to store these files, since he has 30MB space there (for $1).  
twenex
response 137 of 870: Mark Unseen   Jan 2 01:37 UTC 2005

I don't know what the quota is for mail, but he must be over it.
drew
response 138 of 870: Mark Unseen   Jan 2 02:07 UTC 2005

Re #103:
    I am doing the following when the problem occurs:

* Trying to read my mail with pine. Abruptly exits, don't remember the
  message.

* Entering a response in BBS. The editor starts up, but immediately dumps
  upon my typing the first character of the response.

    New information: The problem seems to occur if, and only if, I'm dialed
in direct. I'm entering this response, without problems, via the Net, and Pine
worked normally as well. Just a second ago I tried direct dialing; Pine did
not work and I didn't bother to try using BBS.
twenex
response 139 of 870: Mark Unseen   Jan 2 02:12 UTC 2005

I have a problem while using backtalk. The program refuses to recognize that
not all the items in a conference are new, even when i click on "mark all
responses read".
twenex
response 140 of 870: Mark Unseen   Jan 2 02:14 UTC 2005

Hmm; is your terminal setting ('echo $TERM') the same dialling direct as when
connecting over the net?
drew
response 141 of 870: Mark Unseen   Jan 2 03:12 UTC 2005

Assuming you mean me: TERM is vt100 on
the net. I'm not at home at the moment to
dial in; will check that when I'm there.
gelinas
response 142 of 870: Mark Unseen   Jan 2 03:58 UTC 2005

When a user goes over quota, they have seven days to get back under the quota.
If they don't, quota prevents their creating new files.  Several people are
over quota right now.  They are (mostly) in the grace period.  Some people
are already contacted staff for help.  Others, like Jim through you, find
other ways of dealing with the problem.
keesan
response 143 of 870: Mark Unseen   Jan 2 04:22 UTC 2005

But why does the 'over quota' message appear when you go into pine and not
when you log in?  This is confusing, not helpful.  
cross
response 144 of 870: Mark Unseen   Jan 2 04:25 UTC 2005

This response has been erased.

keesan
response 145 of 870: Mark Unseen   Jan 2 04:31 UTC 2005

Jim had 9MB of files in his home directory and nothing in /tmp and 100K in
the inbox.  I can try to duplicate the problem by downloading a 2MB file to
his home directory if that helps.  I went in and out of pine several times
and kept getting that over quota message every time.  Or maybe he also had
the 9MB in /tmp?  Does it stay there for a week?  
gelinas
response 146 of 870: Mark Unseen   Jan 2 04:39 UTC 2005

Pine was trying to write to a file in his home directory.  That attempt
triggered the quota notification.
drew
response 147 of 870: Mark Unseen   Jan 2 04:53 UTC 2005

When dialing direct:
    Pine exits with "Cannot open terminal capabilities database".
    TERM is set to "dialup". Changing it to "vt100" does *NOT* fix the
problem.
    When trying to enter a response in BBS, spacebar enters a new line, and
typing any other character results in a "Core dumped" followed by "OK to enter
this response?".

    When connected via the internet:
    TERM is set to "vt100".
    Pine and BBS work normally.
drew
response 148 of 870: Mark Unseen   Jan 2 04:55 UTC 2005

Scratch that, TERM is now set to "xterm", logged in from home in Putty under
Windoze 98SE in VMWare. It was "vt100" in ssh on the Zaurus.
gelinas
response 149 of 870: Mark Unseen   Jan 2 04:57 UTC 2005

Try editting your .login to remove the '"$TERM"' from the end of the tset
command.
albaugh
response 150 of 870: Mark Unseen   Jan 2 05:08 UTC 2005

What is the user quota on /tmp ?  Can it be raised?  I'm being thwarted in
sending e-mail with long text (a few 100K characters).
gelinas
response 151 of 870: Mark Unseen   Jan 2 05:11 UTC 2005

The quota on /tmp is 200 KB.  The limit is 1100 KB.
cross
response 152 of 870: Mark Unseen   Jan 2 05:11 UTC 2005

This response has been erased.

cross
response 153 of 870: Mark Unseen   Jan 2 05:12 UTC 2005

This response has been erased.

gelinas
response 154 of 870: Mark Unseen   Jan 2 05:13 UTC 2005

BTW, the command to see _your_ quota is "quota".  Personally, I prefer the
"-v" option:

        quota -v
 0-24   25-49   50-74   75-99   100-124   105-129   130-154   155-179   180-204 
 205-229   230-254   255-279   280-304   305-329   330-354   355-379   380-404   405-429 
 430-454   455-479   480-504   505-529   530-554   555-579   580-604   605-629   630-654 
 655-679   680-704   705-729   730-754   755-779   780-804   805-829   830-854   855-870 
Response Not Possible: You are Not Logged In
 

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