On Thu, Oct 02, 2008 at 07:00:55PM +0530, Rishikesh K. Rajak wrote:
Hi Sudhir/Subrata,
Here you can find one patch which fixes an error in memory controller
testcase.
Description: The testcase return error when run `run_memctl_test.sh`
with no argument.
Signed-off By: Rishikesh K
On Thu, Oct 02, 2008 at 07:00:55PM +0530, Rishikesh K. Rajak wrote:
Hi Sudhir/Subrata,
Hi Rishi,
Here you can find one patch which fixes an error in memory controller
testcase.
I do not find anything that fixes the error you say occured to you.
Description: The testcase return error
On Mon, Oct 06, 2008 at 12:14:26PM +0530, Rishikesh K Rajak wrote:
Description: The testcase return error when run `run_memctl_test.sh`
with no argument.
First you need to know what is the use of the variable passed to the
script. It is the test number which is to be run. So If you are
Mike Frysinger wrote:
1- use of source instead of .
ive fixed all of these with sed ... hopefully i didnt break anything in the
process
OK
2- use of == for comparisons
i see all of one script using == and it's been fixed
OK
3- uname -u (not sure if it is a bashism but dash does
Quoting CAI Qian ([EMAIL PROTECTED]):
Hi,
--- Veerendra [EMAIL PROTECTED] wrote:
This patch addresses the comments if any, on the below files
child_propogate.sh - Propagates the contents of the child sysfs to
parentNS.
parent_share.sh - Creates a sharable volume of the sysfs for
The very first time this testcase is run it fails. Subsequent runs are OK.
AFAICT the problem is that the first time the test runs the semaphore ID
is 0 and thus the line
SEMS=`ipcs -s | awk '{printf %d, $2}' | sed -e 's/ 0//g'`
returns an empty string as the awk output is a sequence of zeros
Mike Frysinger wrote:
ulimit is inherently non-standardized. dash not following bash in argument
compatibility is just dumb.
I totally agree.
does it actually cause the script to abort ? or do you just get a warning
about unknown option ?
It just issue an Illegal option -u message
Hi,
--- Serge E. Hallyn [EMAIL PROTECTED] wrote:
Quoting CAI Qian ([EMAIL PROTECTED]):
Hi,
--- Veerendra [EMAIL PROTECTED] wrote:
This patch addresses the comments if any, on the below files
child_propogate.sh - Propagates the contents of the child sysfs
to
parentNS.
Hi Elder,
It's really a problem on this cases. My solution is to deal with the
semaphore ID with 0 individually.
So I have to separate the semaphore ID with 0 from other IDs.
# ipcs -s -i 0
Semaphore Array semid=0
uid=0 gid=0 cuid=0 cgid=0
mode=0600, access_perms=0600
nsems = 1
