After reboot, the /dev/perfctr file always seems to have the wrong permissions and PAPI fails to initialize. Whats going on?
You are probably running udev, which is not smart enough to know the permissions of dynamically created devices. To fix this, find your udev/devices directory, often /lib/udev/devices or /etc/udev/devices and perform the following actions. mknod perfctr c 10 182 chmod 644 perfctr On Ubuntu 6.06 (and probably other debian distros), add a line to /etc/udev/rules.d/40-permissions.rules like this: KERNEL==”perfctr”, MODE=”0666″ On SuSE, you may need to add something like the following to /etc/udev/rules.d/50-udev-default.rules: (SuSE does not have the 40-permissions.rules file in it.] # cpu devices KERNEL==”cpu[0-9]*”, NAME=”cpu/%n/cpuid” KERNEL==”msr[0-9]*”, NAME=”cpu/%n/msr” KERNEL==”microcode”, NAME=”cpu/microcode”, MODE=”0600″ KERNEL==”perfctr”, NAME=”perfctr”, MODE=”0644″ These lines tell udev to always create the device file with the appropriate permissions. Use ‘perfex -i’ from the perfctr distribution to test this fix.
Related Questions
- After reboot, the /dev/perfctr file always seems to have the wrong permissions and PAPI fails to initialize. Whats going on?
- If I do (right-click) -> Edit on a SBG file, Windows complains about permissions. What is wrong?
- Whenever I try to send a file to another user it always fails. Whats going wrong?
