how to uninstall sudo

[JoonTae Park]

HP-UX 11.i - trusted
I installed sudo and found some problems.
1) once sudo installed, syslog.log file not getting increased.
- means no system log is updated in syslog.log
2) When I login to system, it seems very slow response to get the command prompt. but, uptime is normal.

for 1) I modified /etc/syslog.conf - added a line as below.
local2.debug /var/adm/syslog/sudo
And then,
$touch /var/adm/syslog/sudo
$kill -HUP syslogd_pid
But, nothing changed.

Now, I just want to uninstall sudo.
Anybody to help me?
why it happened, how to uninstall or how to fix these problems.

I'd be appreciate it if you give me any help...

Thanks to read it. ^^

[Pete Randall]

I guess it would depend on how you installed it. If you used swinstall to install the SD depot style package, you would use swremove. If you built it from source, you should be able to just delete it with rm -rf /usr/local/name_of_sudo_dir.


Pete

[JoonTae Park]

Firstly, many thanks for your reply... ^^

When I installed sudo, I didn't use swinstall, but ran configure from sudo source dir.

sudo is located in dir '/usr/local/bin/' and I cannot find any other dirs. or files regarding to sudo in there.
and I'm not sure those problems would be simply resolved with rm -f /usr/local/bin/sudo.

JT

[Jose Mosquera]

Hi,

Try with "swremove" interface:
#swremove

...then select "sudo" software and remove it.

Rgds.

[Geoff Wild]

You will have to go through the Makefile in the src dir and figure out everything it did.....short of that, did you run a make_tape_recovery prior to installing sudo?

Rgds...Geoff

[Patrick Wallek · Accepted solution]

I seriously doubt that sudo caused the problems you are seeing. sudo should have absolutely no impact on the system.

In you case having just compiled the software, you can just remove it. Sudo does nothing special to the kernel and nothing anywhere else.

To test your syslog problem, use the logger command to try to get some message into syslog. If that doesn't work try stopping and restarting syslog with '/sbin/init.d/syslogd stop' and then '/sbin/init.d/syslogd start'.

Your login problem could be anything. The first thing that comes to mind is reverse name lookup and the clients that are connecting. If the server can't resolve the address/name of the PC then that will slow things down.

I think you've got several different problems that need to be addressed separately.