On Tue, 2003-12-09 at 15:14, John Masinter wrote: > Found it!!! > > The answer was in my very first e-mail and none of us caught it. > Remember I am on slackware, and it uses a traditional inetd rather > than xinetd. Traditional unix inetd entries must repeat the executable > path twice, first as the executable field, and then as the first arg. > Otherwise argv[0] will be the first param rather than the exec path. > > This was the case in my inetd.conf, and thus binc would skip argv[0] > expecting it to be the exec path, when really (erroneously) it was the > first param. That's why it was not getting my config file path.
and the 20 million dollar question is.... why use inetd? tcpserver is far better in so many ways. -Jeremy > "The spec said Windows-95 or better...so I installed Linux" cute :D I'll have to remember that -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! ..................... Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
