A. Khattri schreef: > On Wed, 6 Jul 2005, Holly Bostick wrote: > > >>Echo is in the sudo-ed group, and echo isn't the problem-- the problem >>is that permission is refused to write to the file itself (which is an >>error *from* echo, so it would seem that echo itself is OK as far as >>sudo goes). Which means that I have to su anyway, to echo to the file, >>which really isn't the point of the exercise. > > > What is in /etc/sudoers? > > Either the problem is there or maybe its because in some shells, echo is a > built-in command and in others its not (so /bin/echo comes into play). > >
Well, I'm not going to copy my entire file, but I've got /usr/bin/echo sudoed (because that's what 'which echo' said was the path to echo). But doing a locate echo reveals that there is also a /bin/echo.... oh, and la /usr/bin/echo reveals it to be a symlink to /bin/echo. Fine. What in the bloody blue blazes does that tell me? Changing visudo to allow /bin/echo rather than /usr/bin/echo didn't do a thing. I'm using bash, like a boring person. Looking (searching, actually) through man bash, I can see that echo is a built-in-- do I have to sudo bash as well? And in any case, echo isn't refusing to run-- if I run secho $JAVA_HOME, I get a return... but it's the return of the *user's* JAVA_HOME, rather than the *system* JAVA_HOME. This supports my theory that this is a regular su shell and not an su - shell, which is not much help to me in this situation (for echo to write to the /etc/files, I need UID 0). So I suppose I could find this in man sudoers, but that's almost as bad as man bash for trying to find something when you're not quite sure what you're looking for. Is there a way to get sudo to behave as a login shell when sudo-ing rather than just a regular su? And is that a scalable or global change (limitable would be nice)? Holly -- gentoo-user@gentoo.org mailing list
