Hide Forgot
Description of problem: When starting up the oprofile daemon via "opcontrol --start --verbose", if any component of the file names being profiles have path names > NAME_MAX (which happens to be 255 on RHEL3), oprofiled will fail with a ENAMETOOLONG. While this is a limitation of the path names, it might make sense to detect when names are too long, and use some sort of hash to shorten them up. I assume this would also be the case if the entire path was > PATH_MAX (which is 4096 in RHEL3), but I have not tested that to confirm.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.