Well I went further than that. I ran strace against it and it hangs when
it hits the "." entry on the vfat partition which is a win98 partition.
It just goes into an endless loop at that point. And it's not even
slocate's fault, because it loops in a system call (i'll have to go read
my logs again)..
--
Greg Rumple
[EMAIL PROTECTED]
On Mon, 17 Apr 2000, Axalon Bloodstone wrote:
>
>
> On Sat, 19 Jun 1999, Greg Rumple wrote:
>
> > Okay, I upgraded to 2.2.9-27mdk last night on my home box. And awoke this
> > morning to a hung slocate process. I have spent the better part of the
> > day trying to figure out just what it was that was causing it. And I now
> > have it. I have an identical system that didn't have the problem, so I
> > compared to the two trying to figure out the difference. The difference
> > it turns out is I have a vfat filesystem mounted on my home system. If I
> > unmount the vfat filesystem, slocate no longer hangs either. So what
> > could have possibly changed in the vfat filesystem code between
> > 2.2.9-23mdk and 2.2.9-27mdk??? Because it works fine on 23...
> >
> > --
> > Greg Rumple
> > [EMAIL PROTECTED]
> >
>
> Hi there,
> I've been working on this one for awhile now, I have two vfat partitions
> i mount and it passes over the second one without a problem, The first one
> however contains a win98 installation. My first guess was The "@Home.net"
> folder, no luck. Could you please send me some information.
>
> Run /etc/cron.daily/slocate.cron
> change to another console
> Run "ps ax|grep locate"
> note the PID
> ls -l /proc/(insert PID) <- I need output from this
> I need output from "ls -a /mnt/the_vfat_partition"
>
> You will probably want to skip over the vfat partition till I can finger
> this bug, edit /etc/updatedb.conf and /etc/cron.daily/slocate.cron
> in /etc/updatedb.conf just add it to the EXCLUDE
> in /etc/cron.daily/slocate.cron just follow the syntax and tack it on the
> end, should all make sense once you open them.
>
>
>
>
