Whoa, please don't kill the process!  It isn't hung, its building the
historical index.  It will be using 100% CPU for the next few weeks.
Performance will be slightly degraded until then but the system should
be accessible.  Thanks for your patience, it will be worth it -- at
the end we'll finally have a permanently integrated MC history for
every method and class definition.


On Wed, Oct 26, 2016 at 11:00 AM, Fabio Niephaus <lists at fniephaus.com> wrote:
>
> On Wed, Oct 26, 2016 at 5:50 PM Chris Muller <asqueaker at gmail.com> wrote:
>>
>> Just saw this and checked, it's up.  Nothing in the logs, however,
>> daemontools says its only been up for 9200 seconds, which corresponds
>> to the time of your mail.  Very strange..  Not sure if someone shut it
>> down or something else..
>
>
> Tobias apparently logged into the machine and saw the process hanging at
> 100% CPU. He decided to kill it after a few minutes and then it must have
> restarted automatically.
> But thanks for looking into this.
>
>>
>>
>> On Wed, Oct 26, 2016 at 8:11 AM, Fabio Niephaus <lists at fniephaus.com>
>> wrote:
>> >
>> >
>> >
>> >
>>
>
>
>