Greg Hume <ghume @
screamed for help with the following problem:
> Hi all,
> We are at his moment attempting to find the cause to a problem with
> FWTK 1.3. The FTP-GW and HTTP-GW are the services we have configured
> so far. Each time we start the service by connecting to the
> server/firewall we are getting "Statically Linked" messages. The
> messages appear in the log files and on telnet sessions when we telnet
> to the gw service ports. We think it may be an environment problem but
> cannot pin it down.
> The authsvr has successfully been compiled with linking forced to be
> dynamic or static. The gw apps appear work fine in debug mode.
> Any help/advise would be welcome. I really don't wish to scrog the hd
> and rebuild from aaaaaAAARGH.
The problem is not in ftp-gw or http-gw. The problem is in your inetd.conf.
The sample inetd.conf from TIS doesn't work under Linux (I don't know why).
The inetd is not setting up the argv/argc properly when it calls ftp-gw
and this causes ftp-gw to hiccup. All you hafta do is add the name of the
executable to the end of the configuration line in inetd.conf, which gets
passed to ftp-gw as argv. Like this:
ftp stream tcp nowait root /usr/sbin/ftp-gw /usr/sbin/ftp-gw
# this gets passed to ftp-gw as argv
Substitute whatever directory you use for /usr/sbin.
I fought almost half a day with this one. Thought I had really messed up!
Mannesmann Demag Foerdertechnik