I've had this problem across the last two or three releases of FreeBSD.

Currently I'm running:

  bash-2.03$ uname -sr
  FreeBSD 3.2-RELEASE

And whenever I *link* a particular program, sendmail starts complaining!

Nov 29 18:55:53 tuva sendmail[36003]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on 
output channel sending "451 fill_fd: before readcf: fd 1 not open: Bad file 
descriptor": Input/output error
Nov 29 18:55:53 tuva sendmail[36003]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
readcf: fd 1 not open: Bad file descriptor
Nov 29 18:55:57 tuva sendmail[36003]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
readcf: fd 2 not open: Bad file descriptor
Nov 29 19:23:59 tuva sendmail[40563]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on 
output channel sending "451 fill_fd: before main() initmaps: fd 1 not open: Bad file 
descriptor": Input/output error
Nov 29 19:23:59 tuva sendmail[40563]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
main() initmaps: fd 1 not open: Bad file descriptor
Nov 29 19:24:02 tuva sendmail[40563]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
main() initmaps: fd 2 not open: Bad file descriptor
Nov 29 19:24:47 tuva sendmail[42779]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on 
output channel sending "451 fill_fd: before readcf: fd 1 not open: Bad file 
descriptor": Input/output error
Nov 29 19:24:47 tuva sendmail[42779]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
readcf: fd 1 not open: Bad file descriptor
Nov 29 19:25:01 tuva sendmail[42779]: NOQUEUE: SYSERR(bwithrow): fill_fd: before 
readcf: fd 2 not open: Bad file descriptor

The link line looks like this (with the names changed to protect the innocent):

gcc -o /someplace/thing /someplace/thingMain.o /someplace/os_host.o 
/someplace/host_stubs.o /someplace/os_host_stubs.o -L/someplace -lsystem -lcommands 
-lshow -lnewshow -lndm -lscripts -lndmmql -lsystem -lmql -lmib -lmibdb -ltype 
-ltcllite -lutil -ledit -lcompat 

Why would linking a program cause sendmail to complain?  I'm suspicious that
it isn't *entirely* a sendmail problem, since it is triggered by
normal system activity unrelated to mail processing.  If nothing else
it suggest a possible denial-of-service attack doesn't it?  

Suggestions?  Comments?

Searching through the archives shows that at least one other 
person has this problem besides me, and I haven't found a solution
posted.  Reference follow:

http://www.freebsd.org/cgi/getmsg.cgi?fetch=1894326+1897263+/usr/local/www/db/text/1999/freebsd-questions/19990509.freebsd-questions

-- 
Robert Withrow -- (+1 978 288 8256)
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to