Absolutely unbelievable!
I got results to come up by simlinking /var/www/html/htdig to
/usr/share/htdig. Apparently this path is hard-coded in the binaries.
I installed htdig from the Centos 6.7 packages. It wouldn't compile from
source for some reason.


-----Original Message-----
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: Wednesday, September 02, 2015 12:31 PM
To: Jason Fayre <ja...@fayre.me>; mailman-users@python.org
Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman

On 09/02/2015 08:54 AM, Jason Fayre wrote:
> Ok, I will try that.
> What version of htdig are you running?


3.2.0b6 with the rundig.0 patch from
<ftp://ftp.ccsf.org/htdig-patches/3.2.0b6/> and with this patch the source
of which I no longer remember and can't find.

RCS file: /cvsroot/htdig/htdig/htsearch/Collection.h,v
retrieving revision 1.4
diff -r1.4 Collection.h
39c39
<     void Collection::Open();
---
>     void Open();
41c41
<     void Collection::Close();
---
>     void Close();


Also, in an earlier reply I wrote:
>> If you want to make another attempt to access a list archive then go 
>> via the list users information page.
>> 
>> If this problem persists then please e-mail the following information 
>> to the mailman at nfbnet.org:
>>     Referer not known
>>     /mailman/mmsearch/blparent_nfbnet.org
> 
> 
> The above is not familiar to me. It may be a cPanel thing.


Actually, that is also part of the normal expected output from running
mmsearch with no parameters.


-- 
Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to