[3725] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: netscape coredump can cause IRIX panic

daemon@ATHENA.MIT.EDU (t. belton)
Thu Jan 30 14:10:09 2003

Date: Thu, 30 Jan 2003 14:08:20 -0500 (EST)
From: "t. belton" <tbelton@MIT.EDU>
To: Robert A Basch <rbasch@mit.edu>
cc: John Hawkinson <jhawk@mit.edu>, Jonathon Weiss <jweiss@mit.edu>,
        <bug-infoagents@mit.edu>, <release-team@mit.edu>
In-Reply-To: <200301301734.MAA09490@abulia.mit.edu>
Message-ID: <Pine.GSO.4.33L.0301301407421.6532-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I figured Bob was already on the case, as commented in my previous
message. I agree with his analysis and jhawk's comment as well. Let's kill
it.


On Thu, 30 Jan 2003, Robert A Basch wrote:

> > Now that limitting the coredumpsize to 0 is part of the default
> > dotfiles, can we please remove it from the mozilla and netscape
> > scripts? Some of us would like to get core dumps and it's annoying
> > that "unlimit coredumpsize" is insufficient, instead one must use a
> > custom mozilla wrapper.
>
> IIRC, this was added to the netscape wrapper because invoking the
> program via attachandrun (then a setuid program) would reset limits
> to the defaults, at least on IRIX, thus overriding our dotfiles.
> Since (as of 8.4) attachandrun is no longer a setuid program, this
> should no longer be an issue, so there should be no harm in removing
> this limit.  If no one objects, I will make this change soon to the
> mozilla wrapper; I don't think it's worth the bother to change the
> netscape wrapper.
>
> Bob
>
>


home help back first fref pref prev next nref lref last post