Skip to main content
30 events
when toggle format what by license comment
Nov 24, 2019 at 2:01 answer added imz -- Ivan Zakharyaschev timeline score: 13
Apr 13, 2017 at 12:37 history edited CommunityBot
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Dec 18, 2014 at 16:35 answer added JanKanis timeline score: 3
S Jun 13, 2014 at 17:04 history bounty ended jpe
S Jun 13, 2014 at 17:04 history notice removed jpe
Jun 13, 2014 at 16:58 vote accept jpe
Jun 13, 2014 at 14:05 history edited jpe CC BY-SA 3.0
fixed typos
Jun 13, 2014 at 8:30 history edited jpe CC BY-SA 3.0
Improved wording and added a link.
Jun 10, 2014 at 19:25 answer added arnefm timeline score: 15
Jun 10, 2014 at 19:14 comment added Tasos What you are trying to achieve may be impossible and dangerous because you may kill/crash off the process tree anyway as you may run out of your 2gig allocation size. That's why a spawned process is a copy of the parent process.
Jun 8, 2014 at 12:08 comment added mikeserv I completely agree - but I doubt very seriously if I can help you much more - I don't have any practical experience with them. I'm kind of hoping you'll dig into that 7 part series at Linux Weekly News and share your own... That's why - for my part at least - this chat is in the comments block of the question and not an answer...
Jun 8, 2014 at 12:00 comment added jpe @mikeserv It seems the chat is convergeing to something constructive: namespaces is a solution and probably the solution. What remains to be said is how to use them in a user friendly way that would work across most distros with recent enough kernel.
Jun 8, 2014 at 11:34 comment added mikeserv namespaces are containers - just native and handled fully in kernel. And much of the control in control groups is what makes that possible. namespaces finally rolled out production ready circa kernel 3.8. If that last was a small intro - here's the inside out: lwn.net/Articles/531114
Jun 8, 2014 at 9:31 comment added jpe @mikeserv looks like something in the right direction too. But which would be the way that would work in most up-to-date distributions, cgroups or containers/namespaces?
Jun 7, 2014 at 22:21 history tweeted twitter.com/#!/StackUnix/status/475402315843633152
Jun 7, 2014 at 20:53 comment added mikeserv If it's Linux put the parent PID in its own namespace and control it and all its children that way. Here's an introductory answer to that concept: unix.stackexchange.com/a/124194/52934
S Jun 7, 2014 at 19:36 history bounty started jpe
S Jun 7, 2014 at 19:36 history notice added jpe Canonical answer required
Jun 5, 2014 at 12:21 comment added jpe @Gilles OK, let the current question be about Linux as the man page excerpt is from Linux.
Jun 5, 2014 at 11:15 history edited Gilles 'SO- stop being evil'
edited tags
Jun 5, 2014 at 11:15 comment added Gilles 'SO- stop being evil' @jpe Given that different unix variants are likely to do this in very different ways, it would be better to have one question per variant.
Jun 5, 2014 at 6:23 comment added jpe @Gilles It would be good to know how to do it in Linux (the environment where I encountered the problem), but answers for OpenSolaris/Illumos, OSX, BSD are welcome too (e.g. in (Open)Solaris/Illumos it should be easy, right?).
Jun 4, 2014 at 21:56 comment added Gilles 'SO- stop being evil' Under which Unix variant?
Jun 4, 2014 at 13:00 comment added slm Yeah - the tools I'm aware of do not do a group, just single processes, but given how cgroups work for VM technologies like LXC and Docker I'd expect it to do what you want.
Jun 4, 2014 at 12:55 comment added jpe @slm Thanks! Sounds like cgroups is something to try. The only working solution this far (besides an ugly way of summing memory using PS and killing the parent process if above limit) that might work is using some form of a container (lxc or the likes).
Jun 4, 2014 at 12:38 comment added slm I'd take a look at cgroups.
Jun 4, 2014 at 12:37 comment added slm Releated: unix.stackexchange.com/questions/1424/…
Jun 4, 2014 at 7:09 review First posts
Jun 4, 2014 at 7:27
Jun 4, 2014 at 7:06 history edited jpe CC BY-SA 3.0
Added an illustrative example.
Jun 4, 2014 at 6:48 history asked jpe CC BY-SA 3.0