Thank you very much. This solves my issue. On Wed, Jul 17, 2013 at 5:49 AM, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > On 17 July 2013 03:44, kernel kernel <kernel@xxxxxxxxxxxxx> wrote: >> Apologies, >> >> I gave the wrong filename. I'm attempting to read >> >> -r-------- 1 root root 4096 Jul 16 21:03 cpuinfo_cur_freq >> >> as an unprivileged user. Why is this not world readable by default? > > This one actually reads the values directly from the hardware underneath > and so doesn't have permissions for everyone to do it. > > Whereas /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq gets > the value which cpufreq core believes is currently set and so is readable > by everybody. -- Ken O'Brien PhD Researcher Simulation Science and Extreme Events Cluster, 3B1, UCD CASL, 8 Belfield Business Park, Dublin 4, Ireland. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
