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.
Thanks for all the comments!!!
John Masinter wrote:
Summary:
I added some debug output to bincimap-up and it told me that it is indeed getting the command line args from inetd, but it is not parsing them correctly. Any input appreciated.
,,,
(oo)
----------------------o0Oo-(_)-oO0o-----------------------
| John F. Masinter Total Business Computing Inc. |
| Voice: 770-886-9100 x10 Fax: upon request |
| mailto:[EMAIL PROTECTED] http://www.totalb.com |
| P.O. Box 88584 Atlanta, GA 30356 |
------------------------ooO--Ooo--------------------------"The spec said Windows-95 or better...so I installed Linux"
