Please help

Tuskerlove,

Please contact Annette at the Customer Service:

http://www.shrapnelgames.com/cgi-bin...wonderdesk.cgi

She may be able to help you with finding something out about your copy of Dom2, or CD-key, registration, etc.

[alexti]

Originally posted by Graeme Dice:

quote:

---

Originally posted by alexti:
While OS can survive one or 2 deaths of VC, after a dozen or so it apparently runs out of its lives.

Well, if you're writing low-level software, then it's possible to crash just about any OS. Try making an I/O thread that runs at a higher priority than the kernel in *nix based systems for example.

---

The best way to kill *nix that I've experienced was to have bug in "fork" logic that caused my process to multiply exponentially. I've tried to kill them manually, but I was losing the race frantically typing kills. Apparently sysadmin didn't set any quotas on processes, so my application was gradually taking over big Solaris server. Luckily, the server has enough life force to survive until I've paused to think and to figure out that I could do better than doing kills from the console

But I think that a lot of those kind of problems can be protected against on properly configured *nix system. Not if you're writing the kernel yourself, of course, though.

[Norfleet]

Originally posted by alexti:
The best way to kill *nix that I've experienced was to have bug in "fork" logic that caused my process to multiply exponentially. I've tried to kill them manually, but I was losing the race frantically typing kills. Apparently sysadmin didn't set any quotas on processes, so my application was gradually taking over big Solaris server. Luckily, the server has enough life force to survive until I've paused to think and to figure out that I could do better than doing kills from the console

Heh, you mean something like "kill -9 -1"? I'm surprised that it took so long. You'd think that the faster the server was, the faster it would devour its own resources. Although maybe your program wasn't quite as directed as something like "while(1) fork();"

[alexti]

Originally posted by Norfleet:

quote:

---

Originally posted by alexti:
The best way to kill *nix that I've experienced was to have bug in "fork" logic that caused my process to multiply exponentially. I've tried to kill them manually, but I was losing the race frantically typing kills. Apparently sysadmin didn't set any quotas on processes, so my application was gradually taking over big Solaris server. Luckily, the server has enough life force to survive until I've paused to think and to figure out that I could do better than doing kills from the console

Heh, you mean something like "kill -9 -1"? I'm surprised that it took so long. You'd think that the faster the server was, the faster it would devour its own resources. Although maybe your program wasn't quite as directed as something like "while(1) fork();"

---

Yeah, it was much better camouflaged, but they key was that the each process was establishing communication with the spawned process before spawning a new one. This required to do some work before, and as the server was getting loaded more and more whole thing started to slow down which gave me a breath