Sponsored Content
Operating Systems Linux Red Hat Kernel panic after hard reboot and fsck Post 302434816 by fpmurphy on Monday 5th of July 2010 09:05:32 AM
Old 07-05-2010
Looks like it cannot locate the find command. Have you manually checked to see if you can locate this command?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

kernel panic

hello :-) I have one problem with my LiLO... I installed PLD Linux on my computer but when it boots, the last thing I can see is: request_module Root fs not mounted VFS: Cannot open root device 03:01 Kernel panic: VFS: unable to mount root fs on 03:01 and the system stops :-( what... (1 Reply)
Discussion started by: pgas
1 Replies

2. UNIX for Advanced & Expert Users

Reboot after Panic

I've got htis message on our sun U60 machine: "Reboot after panic:errID 0x000004eff........." ,this message have been issued on the /var/adm/messages file & cause system rebooting randomly. Any comment. Thanks, --Nikk (1 Reply)
Discussion started by: nikk
1 Replies

3. Linux

kernel panic

I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies

4. UNIX for Advanced & Expert Users

reboot after panic hp-ux 11o

One of our servers keeps crashing. Here is the following message that we get: 11:01 Thu Aug 31 2006. Reboot after panic: fcpbh_scsi_comp: Inbound data overf low 12:28 Wed Sep 6, 2006. Reboot: 16:12 Wed Sep 06 2006. Reboot after panic: , isr.ior = 0'10240070.0'dcf72938 Does anyone... (1 Reply)
Discussion started by: shoultsc
1 Replies

5. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

6. AIX

Is fsck executed during reboot for AIX?

Dear Gurus, I would like to know if fsck is executed automatically during reboot for AIX? Is there any logs which I can refer to? or any documentation reference for this? Thank You. (2 Replies)
Discussion started by: cteoh88
2 Replies

7. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

8. HP-UX

Reboot After Panic

Hi all, Does anybody know what kinds of events can prompt the following? I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies

9. Solaris

fsck entire hard drive?

ho do you check filesystem on entire hard disk? (9 Replies)
Discussion started by: orange47
9 Replies

10. Solaris

Df reporting double size of du after fsck & reboot

Solaris 8 running on a Sparcstation 5 (Aurora) with 170MHz processor and 256MB ram This is AFTER doing fsck and reboot. 820030k vs 385252k All other files in /usr/asm not in /usr/asm/sys or /usr/asm/data amount to 43k. The /usr/asm/lost+found is 8k. somehow df and other applications... (3 Replies)
Discussion started by: lcoreyl
3 Replies
LOCATE(1)						    BSD General Commands Manual 						 LOCATE(1)

NAME
locate -- find filenames quickly SYNOPSIS
locate [-0Scims] [-l limit] [-d database] pattern ... DESCRIPTION
The locate program searches a database for all pathnames which match the specified pattern. The database is recomputed periodically (usually weekly or daily), and contains the pathnames of all files which are publicly accessible. Shell globbing and quoting characters (``*'', ``?'', ``'', ``['' and ``]'') may be used in pattern, although they will have to be escaped from the shell. Preceding any character with a backslash (``'') eliminates any special meaning which it may have. The matching differs in that no characters must be matched explicitly, including slashes (``/''). As a special case, a pattern containing no globbing characters (``foo'') is matched as though it were ``*foo*''. Historically, locate only stored characters between 32 and 127. The current implementation store any character except newline (' ') and NUL (''). The 8-bit character support does not waste extra space for plain ASCII file names. Characters less than 32 or greater than 127 are stored in 2 bytes. The following options are available: -0 Print pathnames separated by an ASCII NUL character (character code 0) instead of default NL (newline, character code 10). -S Print some statistics about the database and exit. -c Suppress normal output; instead print a count of matching file names. -d database Search in database instead of the default file name database. Multiple -d options are allowed. Each additional -d option adds the specified database to the list of databases to be searched. The option database may be a colon-separated list of databases. A single colon is a reference to the default database. $ locate -d $HOME/lib/mydb: foo will first search string ``foo'' in $HOME/lib/mydb and then in /var/db/locate.database. $ locate -d $HOME/lib/mydb::/cdrom/locate.database foo will first search string ``foo'' in $HOME/lib/mydb and then in /var/db/locate.database and then in /cdrom/locate.database. $ locate -d db1 -d db2 -d db3 pattern is the same as $ locate -d db1:db2:db3 pattern or $ locate -d db1:db2 -d db3 pattern If - is given as the database name, standard input will be read instead. For example, you can compress your database and use: $ zcat database.gz | locate -d - pattern This might be useful on machines with a fast CPU and little RAM and slow I/O. Note: you can only use one pattern for stdin. -i Ignore case distinctions in both the pattern and the database. -l number Limit output to number of file names and exit. -m Use mmap(2) instead of the stdio(3) library. This is the default behavior and is faster in most cases. -s Use the stdio(3) library instead of mmap(2). ENVIRONMENT
LOCATE_PATH path to the locate database if set and not empty, ignored if the -d option was specified. FILES
/var/db/locate.database locate database /usr/libexec/locate.updatedb Script to update the locate database /etc/periodic/weekly/310.locate Script that starts the database rebuild SEE ALSO
find(1), whereis(1), which(1), fnmatch(3), locate.updatedb(8) Woods, James A., "Finding Files Fast", ;login, 8:1, pp. 8-10, 1983. HISTORY
The locate command first appeared in 4.4BSD. Many new features were added in FreeBSD 2.2. BUGS
The locate program may fail to list some files that are present, or may list files that have been removed from the system. This is because locate only reports files that are present in the database, which is typically only regenerated once a week by the /etc/periodic/weekly/310.locate script. Use find(1) to locate files that are of a more transitory nature. The locate database is typically built by user ``nobody'' and the locate.updatedb(8) utility skips directories which are not readable for user ``nobody'', group ``nobody'', or world. For example, if your HOME directory is not world-readable, none of your files are in the data- base. The locate database is not byte order independent. It is not possible to share the databases between machines with different byte order. The current locate implementation understands databases in host byte order or network byte order if both architectures use the same integer size. So on a FreeBSD/i386 machine (little endian), you can read a locate database which was built on SunOS/sparc machine (big endian, net). The locate utility does not recognize multibyte characters. BSD
August 17, 2006 BSD
All times are GMT -4. The time now is 08:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy