[courier-users] Re: Re-using lf_accept in libfilter

2002-01-08 Thread Alessandro Vesely
Sam Varshavchik writes: > Alessandro Vesely writes: > [...] > > [...] Since the patch also modifies libfilter.h, it allows > > a sysv filter to call lf_sysv_accept directly and get 0 to exit, > > or -1 for error, as documented therein. > > Your patch makes no difference as far as the rest of the

[courier-users] Re: Re-using lf_accept in libfilter

2002-01-08 Thread Sam Varshavchik
Alessandro Vesely writes: > Sam Varshavchik writes: >> Your patch does not make any sense. Instead of returning -1, you're >> returning 0, and changing it to -1 in a wrapper function. > > Exactly: that way existing filters don't get broken. > >> In other words, your patch does absolutely no

[courier-users] Re: Re-using lf_accept in libfilter

2002-01-08 Thread Alessandro Vesely
Sam Varshavchik writes: > Alessandro Vesely writes: > > > Sam, > > I have troubles using lf_accept in my filter. That's > > because I to catch a HUP signal by getting out of select > > with errno set to EINTR (the so-called SysV signal semantics.) > > Since lf_accept returns -1 in that case and

[courier-users] Re: Re-using lf_accept in libfilter

2002-01-07 Thread Sam Varshavchik
Alessandro Vesely writes: > Sam, > I have troubles using lf_accept in my filter. That's > because I to catch a HUP signal by getting out of select > with errno set to EINTR (the so-called SysV signal semantics.) > Since lf_accept returns -1 in that case and trusting errno is > not very reliable,