Sorry, that was a typo. Sure, I said sslwrap. As I said, the program runs fine when started from within the debugger. But I can't run sslwrap/gdb from within inetd. Also, sslwrap is intended to make the thing secure, and this behaviour isn't very promising, is it?
Gordon.
It smells like a shared library is missing. Cryptic, I know, it could at
least say so. Strange, though, since it isn't linked against something
special.
This is what it looks like on my SuSE-7.0 system:
for i in ldd file "ls -la"; do $i /usr/sbin/sslwrap;done
libc.so.6 => /lib/libc.so.6 (0x40023000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
/usr/sbin/sslwrap: ELF 32-bit LSB executable, Intel 80386, version 1,
dynamically linked (uses shared libs), not stripped
-rwxr-xr-x 1 root root 760575 Jul 12 04:10 /usr/sbin/sslwrap
The ldd command most likely fails. If so, use strace to see what happens.
Repeat it after running `ldconfig´ as root.
Try `rpm -V sslwrap´. Output means removal and reinstallation of the
package.
Thanks,
Roman.
--
- -
| Roman Drahtmüller