[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gomd-devel] Re: <SCX> working on Secured Cluster-wide eXecution => help

From: Matthias Rechenburg
Subject: [gomd-devel] Re: <SCX> working on Secured Cluster-wide eXecution => help!!!
Date: Mon, 8 Sep 2003 11:24:08 +0200
User-agent: KMail/1.4.3

Hi JP,

On Montag 08 September 2003 00:28, Gian Paolo Ghilardi wrote:
> Hi all.
> As said yesterday, I'm working on SCX.
> Today I spent 8+ h to find a sceure way to spawn procs.
> Now I've a design problem and I need comments.
> Should we provide support to execute programs exiting in a few millisecs
> (like "ls") or support


> _also_ commands requiring long time before quitting (like "updatedb")?

nope (to my mind)

> I'd like to implement the second type but there could be security holes on
> this approach.
> Moreover I've a problem with the output of these progs.
> We can't make the user to wait for the program output, isn't it?
> My (unsuccessful) attempt:
> I fork gomd to execute program ina  separate process.
> I do this so gomd is not forced to waits for program exit.
> But I need the output of teh program.
> The answer should be the pipe.
> So I tried with exec*() family and popen() but, IHMO, the result is not
> good.
> I correctly get the process output but I have no idea how to pass it to the
> parent process (the "real" gomd main process) so the parent can't return it
> to the user.

too complicated ;) just support "short" commands.

> Any idea?
> I don't want to use shmem or something like that...
> Byez.
> <rejected>


E-mail  :  address@hidden
www     : http://www.openmosixview.com
an openMosix-cluster management GUI

If debugging is the process of removing bugs, then
programming must be the process of putting them in.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]