On Sun, 10 Jan 2016, Nils Bruin wrote:
I would argue the opposite, making local accounts is exactly what you
usually do to let users run their own programs (i.e. execute arbitrary
code).
I would agree with that. However, one would also expect that a notebook
server that can manage accounts
On Sunday, 10 January 2016 10:21:34 UTC, Volker Braun wrote:
>
> On Sunday, January 10, 2016 at 8:59:01 AM UTC+1, Jori Mäntysalo wrote:
>>
>> So for multi-user server the admin must make local accounts. This is
>> contrary to all normal systems.
>
>
> I would argue the opposite, making local a
On Sunday, January 10, 2016 at 2:21:34 AM UTC-8, Volker Braun wrote:
>
> I would argue the opposite, making local accounts is exactly what you
> usually do to let users run their own programs (i.e. execute arbitrary
> code).
>
I would agree with that. However, one would also expect that a note
On Sunday, January 10, 2016 at 8:59:01 AM UTC+1, Jori Mäntysalo wrote:
>
> So for multi-user server the admin must make local accounts. This is
> contrary to all normal systems.
I would argue the opposite, making local accounts is exactly what you
usually do to let users run their own programs
On Sat, 9 Jan 2016, William Stein wrote:
SMC has extensive support for this sort of thing with a graphical
interface for configuration... You can control numerous Linux cgroups
parameters, quota, etc.
Good. This answers to my "hidden" question: Has someone thinked about
those things.
On Sa
Which notebook?
* SMC runs in the cloud, no admin needed (sorry ;-)
* Jupyterhub uses normal unix users for permissions and resource limits
* tmpnb uses docker, so containers provide security and resource limits
On Saturday, January 9, 2016 at 8:31:34 AM UTC+1, Jori Mäntysalo wrote:
>
> I a
