At 4:20 PM -0800 3/9/01, Jeremy Lunsford wrote:
> No, as I indicated I compiled it with the --enable-standalone option.
Yes, but it is possible that you are running a different executable.
Try doing a 'make realclean'. Then try to run Qpopper. If you can
run it, you have an old executable. If you can't run it, then try
'./configure' again, then 'make' and try it again.
>
> -----Original Message-----
> From: Randall Gellens [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 4:00 PM
> To: Jeremy Lunsford; Subscribers of Qpopper
> Subject: Re: Running qpopper in standalone mode.
>
>
> At 3:54 AM -0800 3/9/01, Jeremy Lunsford wrote:
>
>> I'm currently trying to get qpopper working in standalone mode.
>> I've compiled it with the following settings.
>>
>> --enable-shy --enable-specialauth --enable-standalone
>>
>> When I attempt to execute the program, I don't get an error on the
>> command line, but I see the following error in my maillog:
>>
>> Mar 9 03:56:24 bender ./popper[32229]: Unable to obtain socket and
> address
>> of client: Socket operation on non-socket (88)
>>
>> Anyone have any thoughts?
>>
>> Thanks...
>
> Perhaps you're running a version that wasn't compiled with standalone mode?
>
>
> --
> Randall Gellens
> Opinions are personal; facts are suspect; I speak for myself only
> -------------- Randomly-selected tag: ---------------
> Every man thinks God is on his side.
> The rich and powerful know he is.
> --Jean Anouilh
