Windows forkbomb protection

[David Markey]

I've been looking for an answer to this everywhere.

How can i protect my terminal server from a simple batch fork bomb. This is trivial on Unix/Linux, but how is it done on windows server?

Thanks.

[Boris]

:( I personally do not know how you would do this on a Windows server,

- but the simple answer would seem to be by placing a limit the number of processes that a single user may own.

If you can do this and a process tries to create another process and the owner of that process already owns more than the maximum you have set, the creation should fail.

You would need to ensure that the maximum was set low enough so that if all the users who might simultaneously bomb a system do so, there will still be enough resources remaining to avoid total disaster

[David Markey]

:( I personally do not know how you would do this on a Windows server,

- but the simple answer would seem to be by placing a limit the number of processes that a single user may own.

If you can do this and a process tries to create another process and the owner of that process already owns more than the maximum you have set, the creation should fail.

You would need to ensure that the maximum was set low enough so that if all the users who might simultaneously bomb a system do so, there will still be enough resources remaining to avoid total disaster

How can i set the maximum number a process a user may own?

[Boris]

Sorry, but

:( I personally do not know how you would do this on a Windows server