On 04/05/2011 09:15 AM, Ivana Hutarova Varekova wrote:
> On 03/14/2011 05:24 PM, Jan Safranek wrote:
>> Added README for the tool test suite
>> Signed-off-by: Jan Safranek<[email protected]>
>> ---
>>
>>   tests/tools/README |   35 +++++++++++++++++++++++++++++++++++
>>   1 files changed, 35 insertions(+), 0 deletions(-)
>>   create mode 100644 tests/tools/README
>>
>> diff --git a/tests/tools/README b/tests/tools/README
>> new file mode 100644
>> index 0000000..b16e541
>> --- /dev/null
>> +++ b/tests/tools/README
>> @@ -0,0 +1,35 @@
>> +libcgroup tools test suite
>> +==========================
>> +
>> +These files should test libcgroup tools, not the libcgroup library itself! 
>> All
>> +the tools use the library so it gets pretty well tested, but that's just a 
>> side
>> +effect, not an intention.
>> +
>> +Usage
>> +-----
>> +
>> +There are few requirements to run this test:
>> + - !!! YOU MUST RUN THE TESTS AS ROOT !!! - the tests need to mount/unmount
> unmount -> umount

IMHO 'unmount' is valid verb, man umount says: 'umount - unmount file
systems'.

>> +   stuff. The tests should not destroy anything important, but use a virtual
>> +   machine if possible, just to be sure.
>> + - You must have no cgroup mounted (i.e. run cgclear before starting the 
>> test
>> +   suite).
>> + - The tests requre various tools to be present in $PATH or at the specified
> requre -> require

Good catch :)

>> +   location, among others:
>> +   diff, awk, su, /bin/bash, /bin/sleep
>> + - The tests require that user and group named 'nobody' exists, some 
>> processes
>> +   with be started with its UID/GID.
>> + - The tests mounts/unmounts cpu, cpuacct, freezer and net_cls controllers.
>> +   Make sure your kernel supports them.
>> +
>> +If you have met all above prerequisites just run 'make check' in this 
>> directory
>> +as root.
>> +
>> +Design
>> +------
>> +There is very simple testenv.sh script, which contains common functions for 
>> all
>> +tests. It includes also simple example how to write a test.
>> +
>> +The tests themselves are just simple shell scripts, which either end with 
>> exit
>> +status 0 (=success) or nozero (=error). The tests should clean after 
>> themselves
> nozero -> nonzero
>> +(incl. unmounting all groups and removing all temp. files).
> unmounting -> umounting
>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>> _______________________________________________
>> Libcg-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/libcg-devel
> 
> 
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Libcg-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libcg-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Libcg-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libcg-devel

Reply via email to