Date: Wed, 20 Jul 2005 01:19:02 +0200 From: Danny Pansters <danny@ricin.com> To: freebsd-ports@freebsd.org, Paul Schmehl <pauls@utdallas.edu> Subject: Re: Problem with Postfix upgrade Message-ID: <200507200119.02863.danny@ricin.com> In-Reply-To: <06543995613FEECBF556C90F@utd59514.utdallas.edu> References: <06543995613FEECBF556C90F@utd59514.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 20 July 2005 00:47, Paul Schmehl wrote: > I just upgraded Postfix on a server, and now I'm getting pipe errors in the > maillog. > > Jul 19 17:38:47 stovebolt postfix/pipe[4354]: fatal: invalid option: ? > Jul 19 17:38:48 stovebolt postfix/master[4180]: warning: process > /usr/local/libexec/postfix/pipe pid 4354 exit status 1 > Jul 19 17:38:48 stovebolt postfix/master[4180]: warning: > /usr/local/libexec/postfix/pipe: bad command startup -- throttling > > Googling reveals that this is apparently a problem with the FreeBSD port > linking with what Weitse calls "a braindead GNU GETOPT". Does anyone know > about this problem? Is it possible to reverse the upgrade without linking > to the same braindead GETOPT? > > How do I fix the problem? > That would suggest that either the port is broken or perhaps not supported on your (4.x?) system. Or that Wietse has a solution for it and that should go into the port (maybe using our libc's getopts rather than gnu's). Someone at some stage probably would like a patch. I don't know more about this to comment any further but this seems to be the scenario at work here. HTH, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507200119.02863.danny>