Results 1 to 6 of 6
Thread: sudo does not read 'make.conf'
Enjoy an ad free experience by logging in. Not a member yet? Register.
sudo does not read 'make.conf'
I have a strange problem with 'sudo'. In my system (if it is not universal feature) I cannot read '/etc/make.conf'. It says 'Permission denied'. I then tried to read with 'sudo' command. But even for 'sudo' it gives the same error. I then did a 'su'. With root login I could read the file.
So, my question is, is 'sudo' any less privilaged than 'su' inspite of assigning ALL=(ALL) ALL to my 'sudo' account?
I tried googling but no help with my problem. Can any of you simulate it on your gentoo system and confirm please?
You should be able to read make.conf without using sudo. My make.conf has permissions rw-r--r--. Have you tried doingCode:
ls -l /etc|grep make"I'm just a little old lady; don't try to dazzle me with jargon!"
No, my problem is not reading the file. My interest is to know how/why 'sudo' and 'su' behave so differently when ALL=(ALL) ALL is set for the sudo account. With that permission, sudo is same as root isn't it? How come I cannot read a file (even if system file) with sudo?
saivin@SV-V1400 ~ $ sudo -l User saivin may run the following commands on this host: (ALL) ALL
Ok, ok, now its working. I'm able to read the make.conf with 'sudo' too. Don't know what happened. The otherday it was not opening and today its working... strange...