>> The monitor door.sudoroom.org (https://door.sudoroom.org/) is currently DOWN
>> (Connection Timeout).
Matthew Senate <mattsenate(a)gmail.com> wrote:
>> I haven't seen this come back up yet. Any reason why this might be
>> disconnected? Any access issues?
> I can't ssh into tamale either. I suspect either hardware or network issues.
UPDATE: sudoroom's network was down. I can access it again now.
Still has an expired certificate though...
> The monitor door.sudoroom.org (https://door.sudoroom.org/) is currently DOWN
> (Connection Timeout).
On Fri, Jun 13, 2014 at 11:33 AM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> I haven't seen this come back up yet. Any reason why this might be
> disconnected? Any access issues?
I can't ssh into tamale either. I suspect either hardware or network issues.
On Sun, Jun 1, 2014 at 3:25 PM, Marc Juul <juul(a)labitat.dk> wrote:
> Oh. I see. It was trying to make a nice .onion address. Well it was using
> 600+ % CPU which probably isn't nice on a shared server? I suspended the
> process. If you feel that it's fine to keep it running then I don't have a
> problem. I don't know what the linode policy is on this.
I think it's fine. It's running at maximal niceness (ionice -c 3 nice
-n 18) so won't impact our own services. That's a good point about
sharing with other customers, I hadn't considered that. The only data
point I can offer about their policy is I have done this on half a
dozen other linode servers and they've never said a word. :)