On Fri, Jul 8, 2011 at 2:43 PM, Cal Leeming [Simplicity Media Ltd] <[email protected]> wrote: > Sorry, I should have given a bit more detail. > > Using ulimit is going to be an issue as it relies on the host allowing > users to modify their ulimit (some aren't allowed). It also then > applies that rule to any other processes within that user, which is > bad as different processes may need different limits.
ulimit doesn't do that. ulimit as a user only allows a user to lower their hard limits to something in the range (0, hard limit). Only super user can increase limits. It also only applies to processes created after ulimit has run. Therefore, your server start script could (probably should) apply limits to the server processes, whilst not affecting the users limits in their shell or other processes. > > I have seen other examples in the past of binaries being wrapped, > which then applied a memory limit, but I can't for the life of me > remember what it was called. :( > It's called ulimit. This is the designed use for it. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
