2009/7/22 Móra Péter <morape...@gmail.com>:
>
> I tried the option server_pool. As I understand, sage can connect to
> other machines to run worksheets on them (to use their resources). I
> would like to run worksheets under different users depending on the
> owner of the worksheet, and in home directories.
>
> Peter
What you want is not implemented. You will either have to implement
it or wait until somebody else does. I likely will in the next 5
months if nobody else does.
server_pool is somewhat close to what you want, since it will run each
user as a different unix user on the *same* Linux box in a round robin
fashion. Just make a bunch of unix accounts foo1, foo2, foo3, ... and
set server pool to ['f...@localhost', 'f...@localhost', ...]
William
>
> On Wed, Jul 22, 2009 at 5:42 PM, Robert
> Bradshaw<rober...@math.washington.edu> wrote:
>>
>> On Jul 22, 2009, at 8:39 AM, Minh Nguyen wrote:
>>
>>>
>>> Hi Peter,
>>>
>>> On Thu, Jul 23, 2009 at 1:35 AM, Peter<morape...@gmail.com> wrote:
>>>>
>>>> Dear Sage Developers!
>>>>
>>>>
>>>> We would like to set up a Sage Notebook server for the students,
>>>> in a
>>>> secure way. How can we do that?
>>>>
>>>> For example if on www.sagenb.org I write
>>>>
>>>> {{{
>>>> %sh
>>>> cat /home/sage/sagenb/sage_notebook/worksheets/any_user_name/0/
>>>> worksheet.txt
>>>> }}}
>>>>
>>>> then I can see the content of other users' first worksheets. I didn't
>>>> try it, but I'm sure I could do damage by deleting files or stoping
>>>> processes (whoami says that I'm user 'worksheet', I assume like
>>>> everbody else is).
>>>>
>>>> I think it would be fine if we could associate logins with linux
>>>> logins, so every user would run codes under his/her own account. This
>>>> would not allow users to delete other users' files.
>>>>
>>>> If every user starts his/her own Sage server with notebook(), then
>>>> it's a waste of memory, they get and error about using the same port
>>>> (they should choose a port at random), and they couldn't share
>>>> worksheets with each others, etc. I think that's not a solution.
>>>>
>>>>
>>>> Any ideas?
>>>
>>> Try this from the Sage command line:
>>>
>>> sage: notebook(secure=True)
>>
>> That's won't help at all for this. What you want to look into is
>> server pools. See the docstring for notebook().
>>
>> - Robert
>>
>>
>> >
>>
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
