[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Sending automatic crash reports to the FSF
From: |
Daniel Colascione |
Subject: |
Re: Sending automatic crash reports to the FSF |
Date: |
Sun, 3 Jan 2016 15:48:16 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 01/03/2016 03:39 PM, John Wiegley wrote:
>>>>>> Daniel Colascione <address@hidden> writes:
>
>> Do you have any idea who would run the servers that would receive these
>> reports? At both Facebook and Microsoft, the resources necessary to store
>> user crash reports are quite significant, and I wouldn't impose that burden
>> on the FSF. We'd definitely need some kind of aggregation and sampling
>> approach.
>
> I rent a VPS that doesn't do a whole lot (mostly just forwards mail and runs
> my personal webblogs). I administer dovecot and postfix on that box, and would
> be happy to receive and store crash reports there.
I run a similar machine. I suspect that both servers would promptly
melt, implode, and then, through sheer energy density, collapse into
black holes. Even in this decadent age, there are a *lot* of Emacs users.
I think we can start with the Emacs-next master branch and get a feeling
for what kind of workload this project would involve.
By the way: Ubuntu (my distribution of choice these days) has its own
crash reporting system, this appport/whoopsie thing. I wonder whether we
can sample their existing Emacs crash reports somehow.
Microsoft also has a way for software vendors to get crash reports from
Windows Error Reporting.
https://wiki.ubuntu.com/ErrorTracker
signature.asc
Description: OpenPGP digital signature
- Re: Crash recovery strategies, (continued)
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Sending automatic crash reports to the FSF (was: Crash recovery strategies), John Wiegley, 2016/01/03
- Re: Sending automatic crash reports to the FSF, Daniel Colascione, 2016/01/03
- Re: Sending automatic crash reports to the FSF, John Wiegley, 2016/01/03
- Re: Sending automatic crash reports to the FSF,
Daniel Colascione <=
- RE: Crash recovery strategies, Drew Adams, 2016/01/03
- Re: Crash recovery strategies (was: Dynamic modules: MODULE_HANDLE_SIGNALS etc.), Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Richard Stallman, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/05
- Re: Crash recovery strategies, Clément Pit--Claudel, 2016/01/05
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/05
- Re: Crash recovery strategies, Clément Pit--Claudel, 2016/01/05
- Re: Dynamic modules: MODULE_HANDLE_SIGNALS etc., Eli Zaretskii, 2016/01/04