--- Joe Brenner <[EMAIL PROTECTED]> wrote:
> 
> Um, one more try here (something really weird
> happened to my
> last post): 
> 
> jack wallen jr <[EMAIL PROTECTED]> wrote: 
> 
> > On Mon, 29 May 2000, Hyung Kim wrote: 
> > > I just removed netscape communicator 4.73 and
> > > installed the communicator 4.73 with 128-bit
> > > encryption.  Now, everytime I try to open
> multiple
> > > copies of netscape, I get a warning stating that
> there
> > > is a lock file in the user's .netscape
> directory.  
> 
> > i changed the way i call netscape.  instead of
> just using the netscape
> > command (say in the gnome panel) to call netscape
> i use this shell script:
> > 
> > #! /bin/sh
> > 
> > if [ -h ~/.netscape/lock ]
> > then
> >   rm -f ~/.netscape/lock
> >   echo "LOCK FILE REMOVED"
> > fi
> > netscape-communicator
> 
> This might be okay for you, but there's a danger
> that you 
> might run a second netscape by accident, in which
> case
> you'll have two netscapes that think they're both,
> for
> example, in charge of your
> ~/.netscape/bookmarks.html file. 
> Don't be suprised if you seem to be getting only
> about half
> of the stuff you try and bookmark (as one netscape
> process
> overwrites the file created by the other one). 
> There's
> reasons for this lock file. 
> 
> Personally I have a script called "dropnet": 
> 
>    #!/bin/sh
>    
>    # dropnet - cleans up after netscape screwups
>    
>    kill -9 `ps | grep netscape | awk '{print $1}'`
>    rm $HOME/.netscape/lock
>    rm $HOME/core >& /dev/null
>    
>    # Note: you might argue that  "killall -9
> netscape-communicator"
>    # would be better than the kill -9 line.
> 
> But neither of these scripts are really the answer
> to 
> Hyung Kim's question.  His point is that there are
> two 
> different versions of netscape 4.73 that behave
> inconsistently.  This sounds like a netscape bug to
> me, 
> and it should probably be reported to them at: 
> 
>      http://help.netscape.com/forms/bug-client.html
> 
> When I switched to Netscape 4.7 (when I upgraded to
> RedHat
> 6.1, I think), I noticed that I could now run a
> second
> netscape without any annoying error messages, and I
> thought:
> "Ah, finally netscape is smart enough to talk to
> existing 
> netscape processes, and it doesn't have to insist on
> being 
> the one and only invocation."  But it's at least
> possible 
> that this new behavior is a bug. 
> 
> Ah, I was just looking at the Release Notes, and I
> see that
> there are two different Linux versions kicking
> around... 
> wouldn't be suprised if this has something to do
> with it: 
> 
>
http://home.netscape.com/eng/mozilla/4.7/relnotes/unix-4.7.html#unix
> 
>    The Linux 2.0 version of Communicator is linked
> against libc
>    5.4.22, libm 5.0.8, and XFree86 3.2. 
> 
>    The Linux 2.0 glibc version of Communicator is
> linked
>    against glibc 2.0.7 and XFree86 3.3.1 
> 
> --
I tried both versions and neither version is smart
enough to run multiple copies of netscape.

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to