[1951] in athena10
Re: irregular mailbox activity
daemon@ATHENA.MIT.EDU (Evan Broder)
Sun Mar 29 19:41:19 2009
Message-ID: <49D006E1.8040407@mit.edu>
Date: Sun, 29 Mar 2009 19:40:17 -0400
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Peter B Whincop <whincop@mit.edu>
CC: linerva@mit.edu
In-Reply-To: <alpine.DEB.1.10.0903291930040.28222@vinegar-pot.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Linerva has been having some ongoing issues with AFS authentication.
We're continuing to look into it, but in the mean time, you should be
able to access your files if you run "aklog" just after you login.
- Evan
Peter B Whincop wrote:
>
> hi evan,
>
> thanks--i am using the correct "which pine." i didn't mv anything, and
> suddenly i have a .pinerc which clearly i have altered. given my reply
> header. but almost all my files are permission denied, and many have
> ?????? instead of permissions. is this normal? it all seems to work in
> athena.dialup.
>
> thanks for any help!
> peter
>
> 09.03.11 23:55 broder@MIT.EDU
>
>> Hi Peter -
>> Linerva switched to using alpine instead of pine, which is a
>> re-write that's unencumbered by licensing. It should mostly be a drop-in
>> replacement for the old pine. Here are a few things to try:
>>
>> Are you sure you're using the version of alpine installed locally on
>> Linerva instead of one installed in a locker? Try running "which pine" -
>> it should be /usr/bin/pine. If it isn't, you can run "add" with no
>> arguments to see which lockers are in your path.
>>
>> If that doesn't work, see if you have a .pinerc file in your home
>> directory. You could try moving that aside and running pine again - it
>> should reconfigure itself to access your MIT mail (you can do this with
>> "mv ~/.pine ~/.pine.old")
>>
>> - Evan
>>
>> peter whincop wrote:
>>>
>>> hi, you have probably heard this from others, but pine cannot access
>>> anything by my actual inbox (in the way i'm used to). it works the
>>> usual way with athena.dialup. just wondering where i might be going
>>> wrong, what log files i could look over to help find a solution.
>>> thanks, peter
>>>
>>
