https://bugzilla.novell.com/show_bug.cgi?id=346469
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=346469#c12
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |vmarsik@novell.com
--- Comment #12 from Neil Brown 2008-05-08 22:46:17 MST ---
Firefox cannot check if it really has a running process in any
other way than trying to lock the file.
As your HOME directory is accessed via NFS, the "other" firefox could
easily be running on a different machine. There is no way for firefox
to find out about that except via NFS locking.
Given that 'reset' causes the problem but 'kill -9' doesn't it seems
most likely that sm-notify isn't being run properly.
When an NFS client gets a lock on a file, it creates a file in
/var/lib/nfs/sm/
with the name of the file matching the server that holds the file.
When the client reboots, it should run sm-notify which should examine
that directory and notify each server that it finds that it has just
rebooted. The servers will then drop any locks that the client held.
That apparently is not happening.
Could you please try the following:
1/ run firefox
2/ ls -l /var/lib/nfs/sm*
this should show two directories: sm and sm.bak.
sm should contain the IP address of the server
3/ press reset and let the machine reboot
4/ ls -l /var/lib/nfs/sm*
if sm-notify has run properly the two directories should be
empty. Alternatively, 'sm.bak' could contain the IP of the server
5/ run /sbin/sm-notify and look at the sm* directories again
6/ see if firefox starts properly.
If you could let me know what happens at each step, I might be closer
to understanding what is happening.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.