SCIENTIFIC-LINUX-USERS Archives

June 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Devin Bougie <[log in to unmask]>
Reply To:
Devin Bougie <[log in to unmask]>
Date:
Fri, 25 Jun 2010 16:13:55 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (14 lines)
Hi Chris,

On Jun 25, 2010, at 4:05 PM, Chris Jones wrote:
> On 25 Jun 2010, at 6:05pm, Devin Bougie wrote:
>> Just incase it helps, we saw this same problem with the Lazarus extension for one of our users.  In this case, the problem appears to have been that ~/.mozilla/firefox was a link to an NFS share.  When I removed the link and moved the firefox directory back into ~/.mozilla/, Firefox 3.6 with Lazarus works fine.  
>> 
>> Firefox 3.0 with Lazarus works fine when ~/.mozilla/firefox is a link to an NFS share, but Firefox 3.6 with Lazarus does not.
> 
> In my case my home directory is itself an NFS mount, nothing can be done about that. ~/.mozilla/firefox is though a regular directory, not a link. Still, $HOME/.mozilla/firefox is ultimately on an NFS share. Is that the problem I wonder...

In our case, home directories are also on NFS shares.  The problem described above happened when ~/.mozilla/firefox was a link to a folder in a different NFS share.  Sorry for the confusion.

Devin

ATOM RSS1 RSS2