What kernel version are you running? We had some issues with kernels prior to 2.4.16 with regard to virtual memory and kupdated that would lock up our database box (not Oracle, but still a database).
If your database is running kinda hard and you start thrashing your filesystem and you have an older kernel, that could be your problem. Also, do you run any kind of NIS or LDAP user information service? If your NIS or LDAP connection gets wacked, that can cause problems too waiting for UID/GID information. Regards, Andy. -----Original Message----- From: Gordon Messmer [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 2:30 PM To: [EMAIL PROTECTED] Subject: Re: FIND command Locks up Redhat System On Fri, 2002-09-20 at 07:46, Brice Hamilton wrote: > > I need to run the standard LINUX/UNIX 'FIND" command to locate > a particular file and when I ran the command, the entire system just > locked up ! Dead as a doornail. Best advice you've been given is to bring the system down and run fsck on the disk. If you find errors, you probably should update all of the errata available for your system, especially the kernel. 7.3 was released with a kernel that will corrupt its filesystem on SMP machines. As for the other advice: * find by itself is fine for /dev and /proc, you just normally don't want to add "-exec grep" or "|xargs grep" into the mix. * recursive symlinks won't be followed forever, the kernel will throw ELOOP after you follow too many symlinks * None of those problems should cause the system to lock up. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
