you are my hero
you are my hero
the-mk
during getting new stubs, one of my clients said this:
after restarting dnetc it continued crunching... not so cool having a quad core sitting there idle...[Jan 11 09:48:35 UTC] The perproxy says: OGR-NG is closed.
[Jan 11 09:48:35 UTC] NetUpdate::All contests are either closed (perproxy) or
disabled (client)
[Jan 11 09:48:35 UTC] Network update is currently not available.
[Jan 11 09:48:35 UTC] *Break* Shutting down...
[Jan 11 09:48:36 UTC] OGR-NG #d: Discarded 26/11-37-13-17-10
(project disabled/closed)
[Jan 11 09:48:36 UTC] OGR-NG #c: Discarded 26/10-9-30-22-45
(project disabled/closed)
[Jan 11 09:48:36 UTC] OGR-NG #b: Discarded 26/10-6-9-11-18
(project disabled/closed)
[Jan 11 09:48:36 UTC] OGR-NG #a: Discarded 26/11-37-13-18-2
(project disabled/closed)
a part of dnetc.ini:
anyone knows what is going on?[networking]
autofindkeyserver=no
keyserver=pproxy.free-dc.org
could it be a bug of "dnetc v2.9102-508-CTR-08122211 for Win32 (WindowsNT 5.1)." (which is prerelease only)?
the-mk
strange indeed... I'm not running windows cuda client, linux instead, but the perproxy's handle both clients and I'm not experiencing any problems with my perproxy, nor it's upline link either. So that is a puzzler.
mine was also a standard and not a CUDA client...
the-mk
From the .plans:
Could be related.Originally Posted by snikkel
makes sense...
the-mk
Bok, could it be that the pproxy is out of order?
from my clients log:
[Jan 18 03:00:01 UTC] The perproxy says: "Free-DC Dnet Proxy!"
[Jan 18 05:00:04 UTC] The keyserver says: "Hai c0w! (cdy)"
[Jan 18 07:00:03 UTC] The keyserver says: "OGR-NG.. Sounds like a new Star Trek series.. (bang)"
the-mk