Greetings. On AIX 7.1 TL5 SP8:
# oslevel -s
7100-05-08-2114
I installed sudo-1.9.5p2-1.ppc:
# yum info sudo
Installed Packages
Name : sudo
Arch : ppc
Version : 1.9.5p2
Release : 1
Size : 17 M
Repo : installed
From repo : AIX_Toolbox
Summary : Allows restricted root access for specified users.
URL : http://www.sudo.ws
License : IBM_ILA
Description : Sudo (superuser do) allows a system administrator to give certain users (or
: groups of users) the ability to run some (or all) commands as root while
: logging all commands and arguments. Sudo operates on a per-command basis. It
: is not a replacement for the shell. Features include: the ability to restrict
: what commands a user may run on a per-host basis, copious logging of each
: command (providing a clear audit trail of who did what), a configurable timeout
: of the sudo command, and the ability to use the same configuration file
: (sudoers) on many different machines.
During install, a symbolic link gets created to sudo_32.
# ls -ltr /opt/freeware/bin/sudo
lrwxrwxrwx 1 root system 7 Sep 8 06:33 /opt/freeware/bin/sudo -> sudo_32
One of our third-party applications that leverages sudo fails unless I manually change the link to sudo_64.
Example error:
Could not load program sudo:
Could not load module /opt/freeware/lib/libintl.a(libintl.so.8).
Dependent module /opt/commvault/Base/libgcc_s.a(shr.o) could not be loaded.
The module has an invalid magic number.
Could not load module sudo_32.
Is there a specific reason why the RPM is delivered with link to sudo_32, rather than sudo_64?
Will this link that I changed be overridden by future updates?
Thank you.
------------------------------
g d
------------------------------