On Tue, 28.04.15 13:49, Mantas Mikulėnas (graw...@gmail.com) wrote:
> On Tue, Apr 28, 2015 at 1:39 PM, Lennart Poettering
> wrote:
>
> > On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
> >
> > > > Moreover, when this is set up
> > > > the mount propagation from the user's nam
On Tue, Apr 28, 2015 at 1:39 PM, Lennart Poettering
wrote:
> On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > > Moreover, when this is set up
> > > the mount propagation from the user's namespace to the rest of system
> > > must be turned off for the root directory, and t
On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
> > Moreover, when this is set up
> > the mount propagation from the user's namespace to the rest of system
> > must be turned off for the root directory, and this will break general
> > assumptions around mounting things through
On Tue, 28.04.15 12:11, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> What if I will just make the / and similar mounts shared?
You have to turn off mount propagation for /tmp, so that the per-user
/tmp instance is not propagated to the rest of the system.
But after turning this off you ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It may be possible, actually. Why oh why btrfs has no per user quotas?
this would be beneficial in some scenarios like this one.
W dniu 2015-04-28 o 12:17, Mantas Mikulėnas pisze:
> On Tue, Apr 28, 2015 at 1:06 PM, Lennart Poettering
> mailto:lenn...
On Tue, Apr 28, 2015 at 1:06 PM, Lennart Poettering
wrote:
> On Tue, 28.04.15 12:03, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
> > (sorry, I haven't sent a reply to the list)
> > What about namespacing and mounting tmpfs per user? You can specify a
> > filesystem size when mounting tmpfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What if I will just make the / and similar mounts shared? Well, I am
not entirely sure about this whole terminology, not sure if I
understand it. About x11, in case of gnome I think a second x server
is spawned to service a request in context of a sess
On Tue, 28.04.15 12:03, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> (sorry, I haven't sent a reply to the list)
> What about namespacing and mounting tmpfs per user? You can specify a
> filesystem size when mounting tmpfs can't you?
Well, you can set this up with some packages for individu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(sorry, I haven't sent a reply to the list)
What about namespacing and mounting tmpfs per user? You can specify a
filesystem size when mounting tmpfs can't you?
W dniu 2015-04-28 o 11:48, Michał Piotrowski pisze:
> Hi,
>
> 2015-04-28 11:39 GMT+02:00
Hi,
2015-04-28 11:39 GMT+02:00 Lennart Poettering :
> On Tue, 28.04.15 00:55, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
> > Hello.
> >
> > I have discovered how to add resource limits for the user, like how
> > much memory the user can use, or how much cpu time.
> > Here is the problem:
On Tue, 28.04.15 00:55, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> Hello.
>
> I have discovered how to add resource limits for the user, like how
> much memory the user can use, or how much cpu time.
> Here is the problem: /tmp seems a way for the user to circumvent this
> restriction. Is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I have discovered how to add resource limits for the user, like how
much memory the user can use, or how much cpu time.
Here is the problem: /tmp seems a way for the user to circumvent this
restriction. Is there a way to protect it too?
-BE
12 matches
Mail list logo
