Kbase 15699: setuid execution not allowed when using progress
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
setuid execution not allowed when using progress
A customer could possibly get the following message even with the
setuid bit set on the progress executables.
Setuid execution not allowed. They will see this message when
going into progress, starting a server and doing a shutdown
of the database. Progress looks likes its working, but the
message always happens. The setuid bit is on the executables.
The problem to look for in this case, is the filesystem. The
filesystem has been mounted with the nosuid. The customer
can check this in one of the following files, /etc/mnttab or
/etc/mtab. Should look for the nosuid for the filesystem where
progress is installed.
#pro test
/root/usr/dlc/bin/_progres: Setuid execution not allowed
#proserve test
/root/usr/dlc/bin/_mprosrv: Setuid execution not allowed
#proshut test
/root/usr/dlc/bin/_mprosrv: Setuid execution not allowed
# more mnttab
/dev/vg00/lvol1 / hfs defaults 0 1 830137281 1
/dev/vg06/lvol12 /root hfs nosuid 0 3 830137313 1
^ ^
| |
| The nosuid on the filesystem.
The filesystem.
To fix the problem you need to umount and then mount the filesystem
with suid enabled.
Progress Software Technical Support Note # 15699