From: William J. H. <wj...@us...> - 2002-04-05 20:13:16
|
Seems to be a problem with some of the latest patches to the IDcheck.sh script. When doing make install with the latest CVS code (synced 3:06 on 04/05/02) I get. -------------------------------------------------------------------------------------------------------------------------- Checking for required user/group ids If any required user ids and/or groups are missing, would you like these created? Y/N Y Bin user id and group exist. Daemon user id and group exist. ************************************** * Required users/groups do NOT exist!!! * * * * Some kernel/syscall tests will FAIL! * ************************************** make: *** [install] Error 1 -------------------------------------------------------------------------------------------------------------------------- The original idea was the only prompt if users/groups needed to be created and then create them. Some part of this seems to be failing. It appears to be a problem with the two lines; id -gn nobody | grep "nobody" > /dev/null On my RedHat system this is fine, but no my SuSE system the group for 'nobody' is 'nogroup'. I will change this to | grep "no" for now so I can continue my tests but perhaps someone will have a better idea? Actually we could just do -g like the other group checks. Now I'm starting to think that the group has to be "nobody" Any comments? j Jay Huie wj...@us... zSeries Linux System Test Phone: 845-435-8164 |
From: William J. H. <wj...@us...> - 2002-04-24 19:09:25
Attachments:
results.out
|
I have corrected what I believe is a small bug in ioctl01.c The exp_enos array was missing one of the conditions, EFAULT. This test is failing when I run it with my automation scripts. One of the first reasons is that on my SuSE system there is no /dev/tty0 simply a /dev/tty. So after changing how it's called in the runtest/syscalls file it will run sucessfully if I am logged in. And the 2nd (more important) reason it's failing is because I am running these tests nohup and logged out, so there is no active tty on the system at all. I seem to recall some changes being made to other tests that were previously using stdin/stdout as 'valid' file descriptors so these would no longer fail when run w/o a controlling terminal. Is this something that can be done for this test? Seems like some of the ioctls are for termio stuff. Thoughts? j PS Incidently, I'm now getting only 18 "failures" if anyone knows about these testcases I'd be happy to work fixing them too. (See attached file: results.out) Index: ioctl01.c =================================================================== RCS file: /cvsroot/ltp/ltp/testcases/kernel/syscalls/ioctl/ioctl01.c,v retrieving revision 1.1 diff -u -r1.1 ioctl01.c --- ioctl01.c 27 Aug 2001 22:15:13 -0000 1.1 +++ ioctl01.c 24 Apr 2002 18:56:40 -0000 @@ -42,6 +42,7 @@ * * HISTORY * 07/2001 Ported by Wayne Boyer + * 04/2002 Fixes by wjhuie * * RESTRICTIONS * test must be run with the -D option @@ -66,7 +67,7 @@ void cleanup(void); void help(void); -int exp_enos[] = {EBADF, EFAULT, EINVAL, ENOTTY, 0}; +int exp_enos[] = {EBADF, EFAULT, EINVAL, ENOTTY, EFAULT, 0}; int fd, fd1; int bfd = -1; Jay Huie wj...@us... Linux System Test Phone: 845-435-8164 |
From: Ming G. <ga...@cn...> - 2003-12-24 05:32:20
|
Hi, Robert, This is Michael from CDSL Plinux test team in China. When we run LTP-20031204 in RHEL 3 Update 1, telnet01 and rlogin01 fail= ed with the following message: ... Starting Host: plinuxt7 spawn telnet plinuxt7^M Trying 172.30.1.70...^M^M Connected to plinuxt7.ppc.cn.ibm.com (172.30.1.70).^M^M Escape character is '^]'.^M^M Red Hat Enterprise Linux AS release 3 (Taroon Update 1 Beta)^M Kernel 2.4.21-6.EL on an ppc64^M login: root^M Password: ^M Last login: Thu Dec 18 13:51:24 from plinuxt4^M ^[]0;root@plinuxt7:~^G[root@plinuxt7 root]# ls -l /etc/hosts | wc -w > /tmp/root.plinuxt7 ^M ^[]0;root@plinuxt7:~^G[root@plinuxt7 root]# CHECKING TELNET STATUS grep: /tmp/root.plinuxt7: No such file or directory ... We noticed the diffs to previous versions at: http://cvs.sourceforge.net/viewcvs.py/ltp/ltp/testcases/network/tcp_cmd= s/telnet/telnet01?r1=3D1.2&r2=3D1.3 http://cvs.sourceforge.net/viewcvs.py/ltp/ltp/testcases/network/tcp_cmd= s/rlogin/rlogin01?r1=3D1.1&r2=3D1.2 = =A0if 1=3D=3D[catch {exec grep -c "9" $TESTLOG/$RUSER.$HOST}] { = = was changed to: = =A0 =A0 =A0 =A0set nummatch [exec grep -c "9" $TESTLOG/$RUSER.$HOST= ] = =A0 =A0 =A0 =A0if {$nummatch=3D=3D1} { = = In the latest version ,"catch" was removed. And we found the previous version can pass. We are wondering whether these changes are necessary? Thanks, Mike= |
From: <hel...@nt...> - 2004-01-09 02:57:33
|
make[4]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/alarm' make[4]: Entering directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/asyncio' cc -Wall -I../../include -g -Wall -I../../../../include asyncio02.c -L.. /../../../lib -lltp -o asyncio02 make[4]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/asyncio' make[4]: Entering directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/bind' cc -Wall -I../../include -g -Wall -I../../../../include bind01.c -L../.. /../../lib -lltp -o bind01 make[4]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/bind' make[4]: Entering directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/brk' cc -Wall -I../../include -g -Wall -I../../../../include brk01.c - L../../../../lib -lltp -o brk01 make[4]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/brk' make[4]: Entering directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/capget' cc -Wall -I../../include -g -Wall -I../../../../include -Wall -g capget01.c -L../../../../lib -lltp -o capget01 In file included from /usr/include/linux/autoconf.h:1, from /usr/include/linux/config.h:4, from /usr/include/linux/fs.h:9, from /usr/include/linux/capability.h:17, from capget01.c:74: /usr/include/linux/rhconfig.h:31:60: operator '(' has no left operand make[4]: *** [capget01] Error 1 make[4]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls/capget' make[3]: *** [all] Error 2 make[3]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel/syscalls' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/ltp-tar/ltp-full- 20040108/testcases/kernel' make[1]: *** [all] Error 2 make[1]: Leaving directory `/root/ltp-tar/ltp-full-20040108/testcases' make: *** [all] Error 2 |
From: Thirugnanam, S. <siv...@in...> - 2004-03-11 15:31:23
|
From: <xu...@da...> - 2004-04-09 08:54:02
|
From: <xu...@da...> - 2004-04-09 09:03:09
|
bHRwLWxpc3SjrMT6usOjoQ0KDQqhoaGhbHRwLWxpc3RAbGlzdHMuc291cmNlZm9yZ2UubmV0IDxs dHAtbGlzdEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQoNCqGhoaGhoaGhoaGhoaGhoaHWwg0KwPGj oQ0KIAkJCQkNCqGhoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaHQ7MP3DQqhoaGhoaGhoaGhoaGh oaGhoaGhoaGhoaGhoaGheHVtaW5nQGRhdGFuZ21vYmlsZS5jbg0KoaGhoaGhoaGhoaGhoaGhoaGh oaGhoaGhoaGhoaGhoaGhoTIwMDQtMDQtMDkNCg== |
From: Bryce H. <br...@os...> - 2004-07-16 03:18:20
|
LTP version LTP-20040506: Patch Name TestReq# CPU PASS FAIL WARN BROK RunTime ---------------------------------------------------------------------- 2.6.7-mm7 294831 2-way 7184 45 3 6 44.0 2.6.7-rc3-mm2 293949 2-way 7223 8 3 6 46.5 osdl-2.6.7 294992 2-way 7223 5 3 3 124.9 patch-2.6.8-rc1 294973 2-way 7184 45 3 6 47.3 LTP version LTP-20040707: Patch Name TestReq# CPU PASS FAIL WARN BROK RunTime ---------------------------------------------------------------------- patch-2.6.8-rc1-bk1 295008 2-way 7191 43 3 6 50.6 patch-2.6.8-rc1-bk2 295025 2-way 7191 41 3 3 125.1 patch-2.6.8-rc1-bk3 295100 2-way 7191 43 3 6 53.8 patch-2.6.8-rc1-bk4 295128 2-way 7191 43 3 6 53.5 2.6.8-rc1-mm1 295081 2-way 7192 41 3 6 48.6 More results + details: http://developer.osdl.org/bryce/ltp/ |
From: Bryce H. <br...@os...> - 2004-08-11 23:23:30
|
Here's an update on the LTP test runs for the kernel. Everything has been looking pretty calm again since Daniel McNeil's fix to the mmap issue last month. Bryce Patch Name TestReq# LTP Ver CPU PASS FAIL WARN BROK RunTime -------------------------------------------------------------------------------- patch-2.4.27-rc2 294321 20040506 2-way 7226 6 3 6 69.0 patch-2.4.27-rc3 294624 20040506 2-way 7226 6 3 6 69.0 linux-2.4.27 295880 20040707 2-way 7234 3 3 6 68.9 patch-2.6.7-bk9 294333 20040506 2-way 7224 7 3 6 46.1 patch-2.6.7-bk10 294403 20040506 2-way 7223 10 3 7 42.9 patch-2.6.7-bk11 294423 20040506 2-way 7178 46 3 6 47.8 patch-2.6.7-bk12 294442 20040506 2-way 7178 46 3 6 47.6 patch-2.6.7-bk13 294511 20040506 2-way 7178 46 3 6 44.4 patch-2.6.7-bk14 294573 20040506 2-way 7178 46 3 6 44.9 patch-2.6.7-bk15 294601 20040506 2-way 7178 46 3 6 48.7 patch-2.6.7-bk16 294614 20040506 2-way 7178 46 3 6 43.5 patch-2.6.7-bk17 294636 20040506 2-way 7178 46 3 6 41.3 patch-2.6.7-bk18 294648 20040506 2-way 7178 46 3 6 45.1 patch-2.6.7-bk19 294733 20040506 2-way 7178 46 3 6 42.6 patch-2.6.7-bk19 294761 20040603 2-way 7063 40 3 3 125.0 patch-2.6.7-bk20 294757 20040506 2-way 7185 46 3 6 46.2 patch-2.6.7-bk21 294926 20040506 2-way 7184 45 3 6 43.0 2.6.7-mm3 294383 20040506 2-way 7185 46 3 6 47.7 2.6.7-mm3 295809 20040707 2-way 7192 41 3 6 53.5 2.6.7-mm4 294485 20040506 2-way 7177 46 3 3 124.9 2.6.7-mm5 294554 20040506 2-way 7178 46 3 6 46.5 2.6.7-mm6 294691 20040506 2-way 7178 46 3 6 45.2 2.6.7-mm7 294831 20040506 2-way 7184 45 3 6 44.0 patch-2.6.8-rc1 294973 20040506 2-way 7184 45 3 6 47.3 patch-2.6.8-rc2 295222 20040707 2-way 7229 5 3 6 52.6 patch-2.6.8-rc3 295778 20040707 2-way 7229 5 3 6 47.4 patch-2.6.8-rc1-bk1 295008 20040707 2-way 7191 43 3 6 50.6 patch-2.6.8-rc1-bk2 295025 20040707 2-way 7191 41 3 3 125.1 patch-2.6.8-rc1-bk3 295100 20040707 2-way 7191 43 3 6 53.8 patch-2.6.8-rc1-bk4 295128 20040707 2-way 7191 43 3 6 53.5 patch-2.6.8-rc1-bk5 295147 20040707 2-way 7191 43 3 6 52.1 patch-2.6.8-rc1-bk6 295171 20040707 2-way 7229 5 3 6 49.6 patch-2.6.8-rc2-bk1 295239 20040707 2-way 7230 3 3 6 49.9 patch-2.6.8-rc2-bk1 295303 20040707 2-way 7301 2 3 3 44.8 patch-2.6.8-rc2-bk2 295334 20040707 2-way 7229 5 3 6 51.6 patch-2.6.8-rc2-bk3 295351 20040707 2-way 7229 5 3 6 55.9 patch-2.6.8-rc2-bk4 295363 20040707 2-way 7229 5 3 6 55.6 patch-2.6.8-rc2-bk5 295377 20040707 2-way 7229 5 3 6 52.5 patch-2.6.8-rc2-bk6 295427 20040707 2-way 7229 5 3 6 52.5 patch-2.6.8-rc2-bk7 295453 20040707 2-way 7229 5 3 6 53.0 patch-2.6.8-rc2-bk8 295515 20040707 2-way 7229 5 3 6 52.5 patch-2.6.8-rc2-bk9 295549 20040707 2-way 7229 5 3 6 47.6 patch-2.6.8-rc2-bk10 295586 20040707 2-way 7230 3 3 6 48.9 patch-2.6.8-rc2-bk11 295612 20040707 2-way 7229 5 3 6 49.9 patch-2.6.8-rc2-bk12 295635 20040707 2-way 7228 8 3 7 51.0 patch-2.6.8-rc2-bk13 295680 20040707 2-way 7229 5 3 6 47.9 patch-2.6.8-rc3-bk1 295798 20040707 2-way 7228 5 3 3 125.1 patch-2.6.8-rc3-bk2 295831 20040707 2-way 7229 5 3 6 51.6 osdl-2.6.7 294992 20040506 2-way 7223 5 3 3 124.9 2.6.8-rc1-mm1 295081 20040707 2-way 7192 41 3 6 48.6 2.6.8-rc2-mm1 295474 20040707 2-way 7229 5 3 6 49.5 -------------------------------------------------------------------------------- * Note: When RunTime > 120 min, this usually indicates a test hung. * For details on any particular test, please access it via http://khack.osdl.org/stp/$TestReq * More info and search tools available at http://www.osdl.org/stp/ Bryce |
From: Bryce H. <br...@os...> - 2004-08-27 22:41:46
|
Here's an update on the LTP test runs for the kernel. Everything has been looking pretty calm. Bryce Patch Name TestReq# LTP Ver CPU PASS FAIL WARN BROK RunTime --------------------------------------------------------------------------------- linux-2.4.27 295880 20040707 2-way 7234 3 3 6 68.9 patch-2.4.27-rc3 294624 20040506 2-way 7226 6 3 6 69.0 2.6.7-mm3 295809 20040707 2-way 7192 41 3 6 53.5 2.6.7-mm6 294691 20040506 2-way 7178 46 3 6 45.2 2.6.7-mm7 294831 20040506 2-way 7184 45 3 6 44.0 patch-2.6.8-rc1 294973 20040506 2-way 7184 45 3 6 47.3 patch-2.6.8-rc2 295222 20040707 2-way 7229 5 3 6 52.6 patch-2.6.8-rc3 295778 20040707 2-way 7229 5 3 6 47.4 2.6.8-rc1-mm1 295081 20040707 2-way 7192 41 3 6 48.6 2.6.8-rc2-mm1 295474 20040707 2-way 7229 5 3 6 49.5 2.6.8-rc4-mm1 296043 20040707 2-way 7224 7 3 6 49.4 linux-2.6.8 296252 20040707 2-way 7229 3 3 3 125.1 linux-2.6.8.1 296304 20040707 2-way 7229 5 3 6 50.2 patch-2.6.9-rc1-bk1 296883 20040707 2-way 7224 7 3 6 52.6 --------------------------------------------------------------------------------- * Note: When RunTime > 120 min, this usually indicates a test hung. * For details on any particular test, please access it via http://khack.osdl.org/stp/$TestReq * More info and search tools available at http://www.osdl.org/stp/ Bryce |
From: <bha...@wi...> - 2005-04-21 12:31:53
|
Hi, Is LTP portable across SUN solaris Frameworks ???? Cause I tried to Build the LTP across SUN systems, but I was unable to do so... =20 But since most of the code is written in ANSI C, Perl and BASH I couldn't figure out why this anamoly ??? =20 Could any one suggest methodologies for Running LTP across SUN O.S . =20 Thanks in Advance. =20 Deepak =20 |
From: Paul L. <pl...@li...> - 2005-04-21 15:44:32
|
On Thu, 2005-04-21 at 18:00 +0530, bha...@wi... wrote: > Hi, >=20 > Is LTP portable across SUN solaris Frameworks ???? Cause I > tried to Build the LTP across SUN systems, but I was unable to do so=85 Given the name "LINUX Test Project", it is generally only expected to work on Linux. I've heard that some others have had limited success running it on other systems, but it's not an explicit goal of the LTP to support anything other than Linux. --=20 Thanks, Paul Larson pl...@li... http://www.linuxtestproject.org |
From: <Ri...@so...> - 2005-06-01 07:27:37
Attachments:
Rishabh Kumar Goel.vcf
|
hi, I am executing LTP on MIPS BOARD. while executing testcases in $LTPROOT/testcases/network/tcp_cmds/sctp/* I get the following error. /ltp-full-20050405/testcases/bin#./test_1_to_1_accept_close test_1_to_1_accept_close.c 1 BROK : socket: Socket type not supported test_1_to_1_accept_close.c 2 BROK : Remaining cases broken test_1_to_1_accept_close.c 3 BROK : Remaining cases broken test_1_to_1_accept_close.c 4 BROK : Remaining cases broken test_1_to_1_accept_close.c 5 BROK : Remaining cases broken test_1_to_1_accept_close.c 6 BROK : Remaining cases broken test_1_to_1_accept_close.c 7 BROK : Remaining cases broken test_1_to_1_accept_close.c 8 BROK : Remaining cases broken test_1_to_1_accept_close.c 9 BROK : Remaining cases broken test_1_to_1_accept_close.c 10 BROK : Remaining cases broken How can I look for the error. Does these testcases require some kind of socket setup in /etc/inetd.conf or etc?=0D Rishabh Kumar Goel The information contained in this e-mail message and in any annexure is confidential to the recipient and may contain privileged information. If= you are not the intended recipient, please notify the sender and delete the message= along with any annexure. You should not disclose, copy or otherwise use the= information contained in the message or any annexure. Any views expressed in this e-mail are= those of the individual sender except where the sender specifically states them to be= the views of SoCrates Software India Pvt Ltd., Bangalore. |
From: <psu...@li...> - 2008-12-04 04:27:42
|
From: Henry Y. <hy...@mv...> - 2009-06-24 22:58:45
Attachments:
splice01.patch
|
Submitting a patch for the splice01 test. Previously the test was checking if the current working directory was NFS based as which the test. The patch changes this test to check whether the test directory is on NFS, as that is actually where the test gets run. Henry Yei (QA) MontaVista Software, Inc. hy...@mv... |
From: Henry Y. <hy...@mv...> - 2009-07-01 20:08:53
Attachments:
syscalls-io.patch
|
It looks like the io_*.sh files are now not needed since the test source has been modified to check for an autoconf definition. This patch modifies the syscalls runtest file to call those test directly. (io_cancel, io_destroy01, io_getevents01, io_setup01, io_submit01) As the scripts are not needed any more, can we remove the following? ltp/testcases/kernel/syscalls/io_cancel01.sh ltp/testcases/kernel/syscalls/io_destroy01.sh ltp/testcases/kernel/syscalls/io_getevents0101.sh ltp/testcases/kernel/syscalls/io_setup01.sh ltp/testcases/kernel/syscalls/io_submit01.sh These scripts were not being copied into testcases/bin anyway and so AFAIK, did not run correctly by pan anyway. Henry Yei MontaVista Software, Inc. hy...@mv... |
From: Stanislav K. <sta...@or...> - 2013-08-05 14:44:41
|
Hi! This is a little fix to run quota_remount_test01.sh with SELinux enabled. Some distros (CentOS 6.x and, likely, RHEL 6) prevent from creation of quota files in 'file_t' directories, some - don't care. I tried this fix on CentOS 5.x/6.x and Oracle Linux, Debian 7. Seems, It's ok, and should not break anything else. And the test couldn't be invoked under 3.x kernels because of its kernel check. Changed it to use tst_kvercmp. |
From: Stanislav K. <sta...@or...> - 2013-08-05 14:44:50
|
From: Stanislav kholmanskikh <sta...@or...> * now it uses tst_kvercmp (to support kernels >= 3) * some distros doesn't allow creation of quota files in directories with SELinux file_t type. Now we explicitly change file type of the test directory to tmp_t Signed-off-by: Stanislav kholmanskikh <sta...@or...> --- .../fs/quota_remount/quota_remount_test01.sh | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git a/testcases/kernel/fs/quota_remount/quota_remount_test01.sh b/testcases/kernel/fs/quota_remount/quota_remount_test01.sh index 98b15d6..7790d16 100755 --- a/testcases/kernel/fs/quota_remount/quota_remount_test01.sh +++ b/testcases/kernel/fs/quota_remount/quota_remount_test01.sh @@ -47,14 +47,8 @@ then fi MNTDIR=$TMPDIR/mnt -uname -r | { - IFS='.-' - read MAJOR MINOR RELEASE REST - if [ "$MAJOR" -lt 2 -o "$MINOR" -lt 6 -o "$RELEASE" -lt 26 ]; then - exit 1 - fi - exit 0; } -if [ $? -gt 0 ]; then +tst_kvercmp 2 6 26 +if [ $? -eq 0 ]; then tst_resm TCONF "Remounting with quotas enabled is not supported!" tst_resm TCONF "You should have kernel 2.6.26 and above running....." exit 0 @@ -83,6 +77,13 @@ mkdir $MNTDIR || die 2 "Could not create the mountpoint" mount -t ext3 -o loop,usrquota,grpquota $IMAGE $MNTDIR || die 2 "Could not mount the filesystem" tst_resm TINFO "Successfully mounted the File System" +# some distros (CentOS 6.x, for example) doesn't permit creating +# of quota files in a directory with SELinux file_t type +if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then + chcon -t tmp_t $MNTDIR || die 2 "Could not change SELinux file type" + tst_resm TINFO "Successfully changed SELinux file type" +fi + quotacheck -cug $MNTDIR || die 2 "Could not create quota files" tst_resm TINFO "Successfully Created Quota Files" -- 1.7.1 |
From: <ch...@su...> - 2013-08-07 11:42:54
|
Hi! > * now it uses tst_kvercmp (to support kernels >= 3) > * some distros doesn't allow creation of quota files in > directories with SELinux file_t type. Now we explicitly > change file type of the test directory to tmp_t Pushed, thanks. -- Cyril Hrubis ch...@su... |
From: <ch...@su...> - 2013-08-05 15:45:52
|
Hi! > * now it uses tst_kvercmp (to support kernels >= 3) > * some distros doesn't allow creation of quota files in > directories with SELinux file_t type. Now we explicitly > change file type of the test directory to tmp_t I can't check that the selinux specific bits works as they should, but general idea of this patch is fine. -- Cyril Hrubis ch...@su... |
From: Stanislav K. <sta...@or...> - 2013-08-07 09:31:46
|
On 08/05/2013 07:45 PM, ch...@su... wrote: > Hi! >> * now it uses tst_kvercmp (to support kernels >= 3) >> * some distros doesn't allow creation of quota files in >> directories with SELinux file_t type. Now we explicitly >> change file type of the test directory to tmp_t > I can't check that the selinux specific bits works as they should, but > general idea of this patch is fine. > So what is the next step? Are we waiting that someone tested and verified its SELinux specific part? Thank you. |
From: Jan S. <jst...@re...> - 2013-08-07 09:42:29
|
----- Original Message ----- > From: "Stanislav Kholmanskikh" <sta...@or...> > To: ch...@su... > Cc: "vasily isaenko" <vas...@or...>, ltp...@li... > Sent: Wednesday, 7 August, 2013 11:31:34 AM > Subject: Re: [LTP] [PATCH] quota_remount_test01: SELinux workaround and other fixes > > > On 08/05/2013 07:45 PM, ch...@su... wrote: > > Hi! > >> * now it uses tst_kvercmp (to support kernels >= 3) > >> * some distros doesn't allow creation of quota files in > >> directories with SELinux file_t type. Now we explicitly > >> change file type of the test directory to tmp_t > > I can't check that the selinux specific bits works as they should, but > > general idea of this patch is fine. > > > So what is the next step? Are we waiting that someone tested and > verified its SELinux specific part? Looks good to me. I gave it a quick try on RHEL6.0 and 7 alpha distro, it worked fine. Regards, Jan > > Thank you. > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > Ltp-list mailing list > Ltp...@li... > https://lists.sourceforge.net/lists/listinfo/ltp-list > |
From: Sean C. <ch...@su...> - 2002-04-05 20:48:20
|
I think it was just added as a convenience, but would prefer to take it out. All of my own use of LTP is on systems installed from a binary vendor CD, so I always have the standard users. I comment-out IDcheck.sh for myself. $.02 -s At 3:13 PM -0500 4/5/02, William Jay Huie wrote: >Seems to be a problem with some of the latest patches to the IDcheck.sh >script. > When doing make install with the latest CVS code (synced 3:06 on >04/05/02) I get. > > >-------------------------------------------------------------------------------------------------------------------------- >Checking for required user/group ids > >If any required user ids and/or groups are missing, would you like these >created? Y/N Y >Bin user id and group exist. >Daemon user id and group exist. >************************************** >* Required users/groups do NOT exist!!! * >* * >* Some kernel/syscall tests will FAIL! * >************************************** >make: *** [install] Error 1 >-------------------------------------------------------------------------------------------------------------------------- > The original idea was the only prompt if users/groups needed to be >created and then create them. > Some part of this seems to be failing. > > It appears to be a problem with the two lines; > id -gn nobody | grep "nobody" > /dev/null > > On my RedHat system this is fine, but no my SuSE system the group for >'nobody' is 'nogroup'. > I will change this to | grep "no" for now so I can continue my tests >but perhaps someone will have a better idea? > Actually we could just do -g like the other group checks. Now I'm >starting to think that the group has to be "nobody" > Any comments? > j > >Jay Huie > wj...@us... > zSeries Linux System Test > Phone: 845-435-8164 > > > >_______________________________________________ >Ltp-list mailing list >Ltp...@li... >https://lists.sourceforge.net/lists/listinfo/ltp-list |