Firefox (1.0.8 & 1.5) leaves behind .parentlock (users with NFS home directories)
Peter Schwenk
directories. When they quit Firefox (1.0.8 & 1.5 mainly) normally,
it leaves its .parentlock file behind, so the next attempt to run FF
will fail with an "already running" message. I believe that 1.0.8
would fail by showing the Profile selection window. I've gotten
around the problem by wrapping the FF startup script in another
script that removes any .parentlock files found in the user's home
directory, but this is really kludgey.
This problem is maddening. I have a gut feeling that this is because
of strange interactions between my Mac OS X Tiger Server file server
and my Linux (Fedora Core 2,3 and SuSE 10) clients, but I don't know
how to pinpoint what's going wrong or what to change to fix it.
Does anyone have some suggestions? Thanks in advance for your incite.
--
- Peter Schwenk
- CITA-3, Systems Administrator
- Mathematical Sciences
- University of Delaware
- (302) 831-0437
- schwenk _at_ math _dot_ udel _dot_ edu
- http://www.math.udel.edu/~schwenk
Nir
probably a Bug :
https://bugzilla.mozilla.org/show_bug.cgi?id=318801
probable solution : create a new profile and
migrate all necessary files to new profile.
To know how to create a new profile :
http://kb.mozillazine.org/Profile_Manager#Linux
migrate all settings from previous folder to new
one :
http://kb.mozillazine.org/Migrating_settings_to_a_new_profile
Start with new profile.
gwtc
Exit [or maybe its close, on linux/mac]
--
Caught Asleep At Your Work Desk
Just in case your boss catches you asleep at your desk, be ready to
blurt out this excuse #1: I was working smarter - not harder.
Nir
Moz Champion (Dan)
> gwtc wrote:
>> its a known problem with closing the program. Try clicking on File,
>> Exit [or maybe its close, on linux/mac]
>>
> ....File >Quit
Windows
File-->Exit
Linux
File-->Quite
Mac
Firefox*-->Quit
*name of program i.e. Thunderbird/SeaMonkey/Mozilla/Safari/Camino - the
menu takes the name of the running program
Moz Champion (Dan)
> Linux
> File-->Quite
Er, um
File-->Quit
Quite <g>
Peter Schwenk
program correctly (i.e. File -> Quit).
> _______________________________________________
> support-firefox mailing list
> support...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-firefox
Peter Schwenk
try it and report back.
> _______________________________________________
> support-firefox mailing list
> support...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-firefox
>
Peter Schwenk
make a new profile directory. I ran Firefox 2-3 times (always
quitting properly, of course). After that, starting Firefox resulted
in the profile selection window popping up (version 1.0.8 seems to do
that when a .parentlock file exists).
This was on a SuSE 10.0 box. I set up a Fedora Core 4 box (also with
NFS mounted home directories), but I don't seem to get the error. I
noticed that the startup script for Firefox differs considerably
between the two distributions of Linux. The Firefox 1.0.8 on FC4
seems to ignore the .parentlock file because it's definitely left
behind.
It seems the FC4 has doctored their startup script to ignore the lock
file. I thought checking for the lock file was a function of the
Firefox binary and not the script used to start the FF binary.
Any ideas about why the lock files get left behind?
On Aug 8, 2006, at 8:15 PM, Peter Schwenk wrote:
> I don't see how creating an additional profile will help, but I'll
> try it and report back.
>
> On Aug 8, 2006, at 4:55 PM, Nir wrote:
>
>> _______________________________________________
>> support-firefox mailing list
>> support...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/support-firefox
>>
>
>
> --
> - Peter Schwenk
> - CITA-3, Systems Administrator
> - Mathematical Sciences
> - University of Delaware
> - (302) 831-0437
> - schwenk _at_ math _dot_ udel _dot_ edu
> - http://www.math.udel.edu/~schwenk
>
>
> _______________________________________________
> support-firefox mailing list
> support...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-firefox
>
Nir
Thanks for your reply . But next time please try
to bottom post while replying . Thanks.
Can you still see '.parentlock' file exist in your
profile folder when Firefox is closed?
"profile selection window popping up" : how many
profiles are listed there? more than one?
If you carefully go through this bug report
(https://bugzilla.mozilla.org/show_bug.cgi?id=318801)
you will find that most people ( who are affected
by this bug ) believe that this problem is
directly related to Network File System.
For example see Comment #30
(https://bugzilla.mozilla.org/show_bug.cgi?id=318801#c30)
Peter Schwenk
I hate bottom posting because one needs to scroll down to see it. Oh
well.
Yes, .parentlock is still there after FF is closed (File->Quit).
Only one profile is shown in the selection box.
I suspect NFS also, but I was hoping to find out the mechanics of how
the .parentlock file is removed and why it would fail. It might give
me incite into what about NFS client (Linux 2.6 kernel) isn't
interacting well with NFS server (Mac OS X).
Thanks!
Nir
newsgroup. See 'Mozilla Forum Etiquette' at
'http://www.mozilla.org/community/etiquette.html'
. Thanks
Yes , it's truly NFS server problem. Some people
found this problem in AFS and some in NFS server.
Something don't let Firefox to access .parentlock
file. It's a basically NFS or AFS server related
problem.
Only thing that i should suggest you is , confirm
this Bug .
Although according to that Bug report , there is
some patch for openAFS (see Comment #28 ).
I'm also agree with ' Jeffrey Altman' ( Comment
#28 ) that this problem occurs because :
"Other file systems may have a similar problem
caused by failing to register
their locks with the Linux kernel. Without the
registration the file system
will not be notified when the lock should be released"
...and i'm afraid that still there is no fix for NFS .