Re: 2.0, loggings, cpu quotas, 2.1 issues, etc.

joost witteveen (joost@rulcmc.leidenuniv.nl)
Wed, 12 Jun 1996 21:29:09 +0200 (MET DST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Sven Geggus: "Re: 2.0 module problem"
Previous message: Jon M. Taylor: "Re: SVGA kernel chipset drivers. (yes, again)"
Next in thread: Alan Cox: "Re: 2.0, loggings, cpu quotas, 2.1 issues, etc."
Reply: Alan Cox: "Re: 2.0, loggings, cpu quotas, 2.1 issues, etc."

>
>
> Re: The CPU quotas...
>
> Max CPU time per process is already supported and has been for a long time.
> See man setrlimit, and note RLIMIT_CPU. This support is in the kernel,
> software support is also needed, and is forthcoming as a config file with
> the Shadow Password Suite.

But as far as I know the CPU time used isn't inherited by the children,
i.e. a malicious user can still fork-bomb, and get as much CPU
time as he likes.

(I'm saying this based on test with bash's ulimit -t, I'm not sure
that's what you were referring to, though).

-- joost witteveen joost@rulcmc.leidenuniv.nl joostje@debian.org

--
Use Debian Linux!

Next message: Sven Geggus: "Re: 2.0 module problem"
Previous message: Jon M. Taylor: "Re: SVGA kernel chipset drivers. (yes, again)"
Next in thread: Alan Cox: "Re: 2.0, loggings, cpu quotas, 2.1 issues, etc."
Reply: Alan Cox: "Re: 2.0, loggings, cpu quotas, 2.1 issues, etc."