Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Virtualization is the way to go; chroot only provides very limited security (no restriction on network, CPU or memory usage). I don't know what virtualization options are available out-of-the-box on CentOS . Commented Dec 17, 2011 at 22:25
  • For limiting memory / cpu usage, maybe look into PAM limits settings. Also, screen can contain any shell and run any command, so are you saying you only want the user to be able to run a persistent irssi instance? Commented Dec 21, 2011 at 2:32
  • @jw013 not exactly, I just want to restrict the user to use only the commands I provide, the example of screen and irssi - so that they couldn't self compile programs and such, and that they don't over use the resources of the computer. Commented Dec 23, 2011 at 11:36