From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: openembedded.net status?
Date: Tue, 12 Aug 2008 14:38:16 +0200 [thread overview]
Message-ID: <g7s07o$o5g$1@ger.gmane.org> (raw)
In-Reply-To: <200808121422.10430.mickey@vanille-media.de>
Michael 'Mickey' Lauer wrote:
> Am Dienstag 12 August 2008 13:47:26 schrieb Koen Kooi:
>> if so, why is it taking so *$($*(@$*(@ long?
>
> No idea. That's the drawback of using donated services. The one in charge of
> colocation is not in germany right now, according to him he notified the
> computing centre, but i have yet to get an update from them. Since I don't
> even have an account at the computing centre, it's a bit tough for me to put
> pressure on those guys.
Thanks, that clears things up a bit. All I knew that is was down and
that there were no messages what happened and what steps are being taken
to fix it.
Isn't there a remote powerswitch that can get flipped like strato has?
> I know it's always annoying when a server goes down, but this arrangement was
> the best we could do and it worked well until now, so let's not freak out and
> hope it's coming back soon.
Can we point DNS back to ltg in the meantime? Having a page saying we're
down is way better than having all website timeout.
regards,
Koen
next prev parent reply other threads:[~2008-08-12 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 11:47 openembedded.net status? Koen Kooi
2008-08-12 12:22 ` Michael 'Mickey' Lauer
2008-08-12 12:38 ` Koen Kooi [this message]
2008-08-12 12:52 ` Michael 'Mickey' Lauer
2008-08-12 12:38 ` Philip Balister
2008-08-12 12:53 ` Richard Purdie
2008-08-12 13:28 ` Michael 'Mickey' Lauer
2008-08-12 15:00 ` Richard Purdie
2008-08-12 17:59 ` Michael 'Mickey' Lauer
-- strict thread matches above, loose matches on Subject: below --
2008-08-12 13:27 Rod Whitby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g7s07o$o5g$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox