Re: broken getopt

2005-08-31 Thread Lowell Gilbert
Robert Fitzpatrick <[EMAIL PROTECTED]> writes: > On Tue, 2005-08-30 at 14:25 -0400, Lowell Gilbert wrote: > > Robert Fitzpatrick <[EMAIL PROTECTED]> writes: > > > Aug 29 11:11:10 esmtp postfix/master[67333]: > > > warning: /usr/local/libexec/postfix/pipe: bad command startup -- > > > throttling >

Re: broken getopt

2005-08-30 Thread Robert Fitzpatrick
On Tue, 2005-08-30 at 14:25 -0400, Lowell Gilbert wrote: > Robert Fitzpatrick <[EMAIL PROTECTED]> writes: > > Aug 29 11:11:10 esmtp postfix/master[67333]: > > warning: /usr/local/libexec/postfix/pipe: bad command startup -- > > throttling > > Aug 29 11:11:51 esmtp postfix/master[67333]: > > warning

Re: broken getopt

2005-08-30 Thread Lowell Gilbert
Robert Fitzpatrick <[EMAIL PROTECTED]> writes: > > > Victor referred me to the archives after finding out I have linked > > > Postfix with a broken GNU getopt(), but I have not been able to come up > > > with the solution. My current getopt package is gengetopt-2.11, should I > > > resort to an ea

broken getopt

2005-08-29 Thread Robert Fitzpatrick
> > Victor referred me to the archives after finding out I have linked > > Postfix with a broken GNU getopt(), but I have not been able to come up > > with the solution. My current getopt package is gengetopt-2.11, should I > > resort to an earlier version and re-compile Postfix? > > > > Look at

[Fwd: Re: broken getopt]

2005-08-29 Thread Robert Fitzpatrick
Forwarded Message > > Victor referred me to the archives after finding out I have linked > > Postfix with a broken GNU getopt(), but I have not been able to come up > > with the solution. My current getopt package is gengetopt-2.11, should I > > resort to an earlier version and re