On Sun, Feb 14, 2010 at 11:59 PM, vishwanath govind
<[email protected]> wrote:
> Yes, I checked this before, It return errorno "0". Somehow mknod02 won't
> display the errorno when it exit with "tst_brkm(TBROK, cleanup, "%s not in
> /etc/passwd", LTPUSER)" but I have similar tests return errorno 0. I see
> "nobody" user and uid/gid -99 is present in /etc/passwd file. Do I need to
> enable anything in KERNEL config or /etc?
>
> ============================log===============================
> <<<test_start>>>
> tag=nftw01 stime=1170483127
> cmdline="nftw01"
> contacts=""
> analysis=exit
> <<<test_output>>>
> nobody not found in /etc/passwd: No such file or directory
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=1 cstime=2
> <<<test_end>>>
> <<<test_start>>>
> tag=nftw6401 stime=1170483127
> cmdline="nftw6401"
> contacts=""
> analysis=exit
> <<<test_output>>>
> change_owner: nobody not found in /etc/passwd: No such file or directory
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=2 cstime=1
> <<<test_end>>>
> ==============================end==================================
> Regards
> Vishwa
>
> On Mon, Feb 15, 2010 at 12:50 PM, Garrett Cooper <[email protected]> wrote:
>>
>> On Sun, Feb 14, 2010 at 11:09 PM, vishwanath govind
>> <[email protected]> wrote:
>> > Garrett,
>> >  Thanks for your quick reply. I am using "ltp-full-20091231".
>> > Regards
>> > Vishwa
>> >
>> > On Mon, Feb 15, 2010 at 12:33 PM, Garrett Cooper <[email protected]>
>> > wrote:
>> >>
>> >> On Sun, Feb 14, 2010 at 10:51 PM, vishwanath govind
>> >> <[email protected]> wrote:
>> >> >
>> >> > Hi,
>> >> > I am facing common issue which causing many of the LTP syscalls test
>> >> > cases
>> >> > to fail. I have taken mknod02 test to show this issue here.
>> >> > Definitely I
>> >> > am
>> >> > missing something out here, could you guys please point me to right
>> >> > direction?  Please let me know if you need some more info/log
>> >> >
>> >> > ======================log================================
>> >> > # ls /etc
>> >> > group   passwd
>> >> >
>> >> > # ./IDcheck.sh
>> >> > Checking for required user/group ids
>> >> > 'nobody' user id and group found.
>> >> > 'bin' user id and group found.
>> >> > 'daemon' user id and group found.
>> >> > Users group found.
>> >> > Sys group found.
>> >> > Required users/groups exist.
>> >> >
>> >> > # cat /etc/passwd
>> >> > root:x:0:0:root::
>> >> > nobody:x:99:99:nobody::
>> >> > bin:x:1:1:bin::
>> >> > daemon:x:2:2:daemon::
>> >> >
>> >> > #uname -a
>> >> > Linux (none) 2.6.29 #4 PREEMPT Thu Feb 11 23:37:46 PST 2010 armv6l
>> >> > GNU/Linux
>> >> >
>> >> > # ./mknod02
>> >> > mknod02     1  TBROK  :  nobody not in /etc/passwd
>> >>
>> >> What version of LTP is this?
>>
>> That's a lousy diagnostic, as any one of the following errors could be
>> the culprit:
>>
>> ERRORS
>>       0 or ENOENT or ESRCH or EBADF or EPERM or ...
>>              The given name or uid was not found.
>>
>>       EINTR  A signal was caught.
>>
>>       EIO    I/O error.
>>
>>       EMFILE The maximum number (OPEN_MAX) of files was open already
>> in the calling process.
>>
>>       ENFILE The maximum number of files was open already in the system.
>>
>>       ENOMEM Insufficient memory to allocate passwd structure.
>>
>>       ERANGE Insufficient buffer space supplied.
>>
>> What are the permissions on the file and is there any way where you
>> could grab the latest copy of the file from git and try that out (the
>> patch is available at:

Nope... you sure your ldap / nis isn't busted?
-Garrett

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to