I get a problem starting up
Netscape.
The problem is with a "lock" file, right? When Netscape starts
up, it pops up a window that says:
Netscape has detected a /home/username/.netscape/lock file
(With your username as the second element of the path.) It then
gives you information about where the other Netscape process is,
and what to do about it. The information is actually pretty clear
and accurate. Here's some of the background.
It's bad to have two Netscapes running at once, because they step
all over each other. They're both fighting to control your
bookmarks file, history file, disk cache and so forth. So,
Netscape tries to avoid this situation.
Here's how it works:
- When Netscape starts up, it checks to see if a "lock" file
exists. Normally, the file doesn't exist. If the file exists,
Netscape gives you the error message.
- Assuming the "lock" file doesn't exist, Netscape creates it,
putting in it information about the host the process is
running on and the process ID number (PID). This is so that
the previous step will work if any other netscape starts up.
- When Netscape exits, it deletes the lock file.
All this is fine, but if Netscape crashes, it never gets to delete
the file, so the next time you run it, you'll get this warning.
So, as the instructions say, first check to see if you have
another netscape running. If you don't, it's safe to remove the
file and run netscape normally.
rm ~/.netscape/lock