sudo problem with csh

Todd C. Miller Todd.Miller at
Thu Mar 30 12:26:04 EST 2000

It sure sounds like /opt/sudo/bin is simply not in your $path.
Note that sh/ksh uses $PATH (colon separated) whereas csh uses $path
(a space separated list).

I bet if you do:
    set path = ( $path /opt/sudo/bin )

You will be able to just run 'sudo' instead of giving a full path.
On HP-UX the default path for csh is usually set in /etc/csh.login,
although that *should* pull in /etc/PATH.

 - todd

In message <BD8AC1BB8374D311A74200508B5A914F4651F0 at>
	so spake "Wright, Richard" (RWright):

> I just installed sudo on my HP-UX 11.00 system. The sudo command works good
> when in ksh. 
> In csh I have to type "/opt/sudo/bin/sudo" to get it to work. If I just type
> "sudo", I get a "not found" error. I can then enter "type sudo" and the full
> pathname is returned.
> I have verified my /etc/PATH.
> I have verified permissions on /opt/sudo/bin/sudo which are ---s--x--x root
> root.
> I have what I believe is a work around. I created a symbolic link with "ln
> -s /opt/sudo/bin/sudo /opt/sudo/sbin/sudo" and now it works. (NOTE: sbin vs.
> bin)  According to the "ln" man page, there is no problem with having 777
> permissions on the link. 
> Quote from "man ln"...
> "Symbolic links are created with the ownership of the creator and the
> permissions are of the creator's current umask.  Once created, the symbolic
> link ownership and permissions will not change, since the  mode and
> ownership of the symbolic link is ignored by the system."
> Please let me know if you can shed some light on the cause of this problem,
> or if you have a solution or a better work around.
> Thanks
> Richard Wright
> Hussmann, Corp
> "The views, opinions, and judgments expressed in this message are solely
> those of the author. The message contents have not been reviewed or approved
> by my employer."

More information about the sudo-users mailing list