On Tue, 2006-09-19 at 11:32 -0400, [EMAIL PROTECTED] wrote:
> On Thu, 14 Sep 2006 18:38:33 PDT, Rohit Seth said:
> 
> (Sorry for the late reply...)
> 
> 
> > --- linux-2.6.18-rc6-mm2.org/Documentation/containers.txt   1969-12-31 
> > 16:00:00.000000000 -0800
> > +++ linux-2.6.18-rc6-mm2.ctn/Documentation/containers.txt   2006-09-14 
> > 17:13:48.000000000 -0700
> 
> > +5- Remove a task from container
> > +   echo <pid> rmtask
> 
> echo <pid> > rmtask
> 
> is what I think was intended.  Also, I'm not sure <pid> is the best
> meta-syntax - anybody got a better idea?
> 

Fixed that.

> > +9- Freeing a container
> > +   cd /mnt/configfs/containers/
> > +   rmdir test_container
> 
> What happens if you try to remove a container that still has active tasks? Are
> you relying on the VFS to catch the 'non-empty directory'? (of course, 'rm -r'
> has predictable semantics here).
> 

When a rmdir operation is done on a directory, then all tasks have to
move out of container (before we the rmdir operation is complete).  This
removal of tasks from a container is done as part of
container_remove_tasks.

> I see support for "add a task" and "remove a task", but none for listing
> the current tasks in the container?

This is one of the TODO items that I've listed.  Will be there soon.

thanks,
-rohit


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech

Reply via email to