Why does the kernprof command say,”/dev/profile: No such file or directory”?
The most obvious reason why the kernprof command gets a /dev/profile: No such file or directory error is that there really is no /dev/profile node. First, ensure that the node exists. If it doesn’t, you must create it: mknod /dev/profile c 192 0 If /dev/profile does exist and you still see the No such file or directory error, then the currently executing kernel is most likely *not* the kernel that you built with the profile patch applied to it. Doublecheck the build, doublecheck that you actually executed /sbin/lilo to install the kernel image, and doublecheck that you booted this patched kernel. Consider editing the high level Makefile to append “-kernprof” to the EXTRAVERSION symbol, which would then allow you to do a “uname -a” and to gain extra confidence that you’re really executing the kernel that you think you are.
Related Questions
- if I have a file x.php in my www directory, what should I put as the command in the standard cron jobs section to run that file?
- Who can submit products, company profile into manufacturers directory and products catalog?
- Why doesn the OUTFILE command automatically create the directory for the output file?
