[7942] in testers
Re: AFS Weirdness
daemon@ATHENA.MIT.EDU (Adam Seering)
Sat Mar 14 11:09:24 2009
Message-ID: <49BBC853.5020609@mit.edu>
Date: Sat, 14 Mar 2009 11:08:03 -0400
From: Adam Seering <aseering@MIT.EDU>
MIME-Version: 1.0
To: Jonathan Reed <jdreed@mit.edu>
CC: Geoffrey Thomas <geofft@mit.edu>, testers@mit.edu
In-Reply-To: <E1555AA1-4C36-465E-B722-B0F4F4744805@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 3/14/09 10:23 AM, Jonathan Reed wrote:
> What does "grep EnableIndexing ~/.config/tracker/tracker.cfg" say?
EnableIndexing=true
Should I set that to "false"? Curious, what's actually going on here?;
why does an indexer break AFS?
Thanks,
Adam
>
> -Jon
>
> On Mar 14, 2009, at 10:17 AM, Geoffrey Thomas wrote:
>
>> Are you running a trackerd process? Try running 'pkill trackerd', and
>> see if that makes the AFS weirdness go away.
>>
>> New users shouldn't have trackerd, but you've probably logged your
>> Athena account in to a pre-Intrepid Ubuntu machine and gotten the old
>> default (i.e., on).
>>
>> --
>> Geoffrey Thomas
>> geofft@mit.edu
>>
>> On Sat, 14 Mar 2009, Adam B Seering wrote:
>>
>>> Hey again,
>>> I've been trying to print an 11x17" PDF from DebAthena this morning.
>>>
>>> First, Evince doesn't appear able to do this...; I can't seem to find
>>> a way to specify paper size.
>>>
>>> Second, I've been trying to open one of (xpdf, acroread) to test this
>>> out. At first, I was getting weird errors trying to "athrun acro
>>> acroread". This has progressed to completely random AFS errors,
>>> typically of the form "FOO: No such file or directory", where FOO
>>> clearly exists (it may or may not show up with "ls"). Right now, my
>>> home directory has even ceased to exist, so "cd ~" errors out. (On
>>> that note, I should probably log out while I still can...) This seems
>>> to have been getting progressively worse; I used to be able to cd
>>> into /mit/outland/arch/, but no longer can.
>>>
>>> I do have Kerberos tickets and AFS tokens; I just did "kinit ; aklog"
>>> and it didn't fix the problem. ("aklog sipb" didn't help either, with
>>> SIPB-cell lockers.)
>>>
>>> This was on W20-575-6.
>>>
>>> Enjoy,
>>> Adam
>>>
>>>
>>>
>>>
>>>
>
>
