On Mon, May 18, 2015 6:30 pm, Todd C. Miller wrote: > Currently, "chroot -u" doesn't use the settings in /etc/login.conf.
Nice. I was missing this option. > > Open questions: > > 1) Should this just be default behavior with -u? Are there cases > when you would *not* want to set the priority and resouce limits > based on the target user when one is specified? When I was setting up an application in a chroot, my expectation was that -u would apply that user's class. When I noticed that it didn't, I looked for a -c to set the class, which didn't exist. So I would vote for the class being set by default and -c to override it. I believe this is what su does...? Tim.
