Bug 701157

Created attachment 496083 [details]
File: backtrace

I tried to reproduce this bug, but without any success. Are you able to reproduce it at will? Is dir_x somehow special? Extra big? Files with special encoding or something?

(In reply to comment #2)
> I tried to reproduce this bug, but without any success. Are you able to
> reproduce it at will?
Yes! Absolutely!

> Is dir_x somehow special?
It is within a vfat filesystem
> Extra big?
60+ GB.
> Files with special encoding or something?
Contains media files and some text files describing the media files.
The media files are mostly mp3, with a smattering of flac, mp4, flash.

I do not know what was causing it,
but I modified the script, and now it all works just fine.
Here is the modified script:


typeset -fx sizeof
integer __fisize__
__fsize__=0
export __fsize__
function sizeof
{
        __fsize__=`/bin/ls -l "$1" | awk '{ print $5 }'`
}

integer max
integer tsize
integer n
integer size
max=4718582000
tsize=0
size=0
n=0
flist=list$n
rm -rf list*
find dir_x -type f | while read f; do
        sizeof "$f"
        tsize+=$__fsize__
        echo size = $__fsize__   tsize = $tsize    max = $max    flist = $flist
        if [ $tsize -gt $max ]; then
                n+=1
                flist=list$n
                tsize=$__fsize__
        fi
        echo "$f" >> $flist
done


I had thought that when a kshell function returns a value,
that that value should be returned to the caller. 
It seems that that is not the case.
It seems that ksh funcs can no longer return a value.
To test that,  I created a simple function on the command line:

function xx
{
         return 0
}

and my shell immediately exited and that kill my gnome terminal.

So, I changed the function sizeof
and made it to export the variable __fsize__ and let the caller
simply use  $__fsize__
That fixed the problem.

PS: I am using ksh-20110208-3.fc14.i686


Thanx

I've tried it with huge directories, but it was working fine.

Could you try whether updated package works for you?

http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/

you can update ksh using following command (as root):

rpm -Fvh http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/ksh-debuginfo-20110505-1.fc14.i686.rpm http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/ksh-20110505-1.fc14.i686.rpm

(In reply to comment #5)
> I've tried it with huge directories, but it was working fine.
> 
> Could you try whether updated package works for you?
> 
> http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/
> 
> you can update ksh using following command (as root):
> 
> rpm -Fvh
> http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/ksh-debuginfo-20110505-1.fc14.i686.rpm
> http://kojipkgs.fedoraproject.org/packages/ksh/20110505/1.fc14/i686/ksh-20110505-1.fc14.i686.rpm

Could you please tell me where I can get the koji .repo files?
That way, I can update with yum.

There are no repo files for koji. Buildsystem contains tons of packages where new packages are created every few minutes and old ones deleted. Also not all packages that maintainer builds should be used by users. So there is not a such repository. When using packages from koji, you can:
a) use rpm -Uvh / -Fvh with links to rpms

b) download packages manually and use rpm -Uvh / -Fvh package1.rpm package2.rpm ...

c) download packages manually and use: yum localupdate --nogpgcheck package1.rpm package2.rpm ...

Anyway, this time, I've pushed this version to updates testing repository, because I've verified it fixes different bug, so you can use:

yum update --enablerepo=updates-testing ksh

but it'll take a few hours before this package gets in repository and mirrors get synced

Needinfo state for a loong time. Also Fedora 14 is no longer supported. Closing.