Well this is sort of the standard unixy way of doing things.
One process per task.
Ultimately I was thinking of the xinetd model.
My controlling process
would spawn a sage process when a user logs in
(whatever that would mean), and probably perform
an appropriate redirect.
There are of course
On Jun 6, 2:04 pm, Michel [EMAIL PROTECTED] wrote:
Input from my son who is fascinated by security.
On my setup at least the notebook user can
kill the sage binary, needing manual intervention
to start it again.
How to guard against that?
Michel
Well instead of starting
su -
Yep this solution seems to work quite well. My son remarked
that when restarting sage it is necessary to also kill all processes
run by sageuser. Otherwise sageuser could start a process which
would be on the lookout for new instances of sage and kill
these also!
Michel
On Jun 6, 6:40 pm,
Hi,
The better solution -- in the long run -- is that each SAGE worksheet
process starts as a different more limited user. Unfortunately, this
will require significant work to implement -- we'll likely do it
at SD4 next week.
William
On 6/6/07, Michel [EMAIL PROTECTED] wrote:
Yep this
Yes, I agree. But one has to guard against the user
killing his own sage process. Is it possible to prevent this?
If this is not possible then any solution will be basically
equivalent to mine (restarting the sage process of the user).
Implemented within sage of course instead of a shell
script.
On 6/6/07, Michel [EMAIL PROTECTED] wrote:
Yes, I agree. But one has to guard against the user
killing his own sage process. Is it possible to prevent this?
If this is not possible then any solution will be basically
equivalent to mine (restarting the sage process of the user).
Implemented
Are you sure what you say is true?
I mean doing
sage: import os
sage: os.system(whoami)
server2
sage: os.system(ps -u server2)
PID TTY TIME CMD
6418 ?00:00:00 sh
6419 ?00:00:00 sage
6425 ?00:00:00 sage-sage
6439 ?00:00:00 sage-run
6440 ?
Ok I see. I wasn't aware that one sage process
(your server process) could serve multiple users.
I will wait to see how things develop.
===
In the setup I was planning it is definitely not true that any user
can kill
the server process. I wanted to have a bunch of
On 6/6/07, Michel [EMAIL PROTECTED] wrote:
Ok I see. I wasn't aware that one sage process
(your server process) could serve multiple users.
I will wait to see how things develop.
===
In the setup I was planning it is definitely not true that any user
can kill
Well this problem I could solve. They were caused by an /etc/mtab
file which was out of sync, making mount -a believe some
filesystems were mounted when they weren't.
I have now a running setup. The only problem is that one has
to be root to do chroot in Fedora. So I created a user sage
inside
On 6/5/07, Michel [EMAIL PROTECTED] wrote:
Well this problem I could solve. They were caused by an /etc/mtab
file which was out of sync, making mount -a believe some
filesystems were mounted when they weren't.
I have now a running setup. The only problem is that one has
to be root to do
On 6/5/07, Michel Van den Bergh [EMAIL PROTECTED] wrote:
Hi.
I have things running pretty well now. Below are my notes.
Perhaps they can posted on the Wiki somewhere (in polished form).
Could you make a new section of the SAGE install
guide and send me a patch? To do this:
(1) cd to
12 matches
Mail list logo
