Fmota Tech

On Sunday 22 April 2012 03:34:35 Noel Butler wrote: Hi Noel:

At the risk of becoming a real pest, can you tell me what version of PCRE you used? I installed PCRE-8.30 and PHP 5.3.10 will not compile with it. PHP-5.4.0 was OK but with PHP-5.3.10 I get

/tmp/php-5.3.10/ext/pcre/php_pcre.c:258: undefined reference to `pcre_info’ collect2: ld returned 1 exit status make: *** [sapi/cli/php] Error 1

The PHP config file has this entry:

Andrei POPESCU wrote:

That won’t work because the saved part is the *body* of the part and not the raw encoded bits of that part. It is the raw encoded part that is signed, not the decoded body.

See my earlier response in this thread where I showed how this can be done manually.

http://lists.debian.org/debian-user/2012/04/msg00766.html

Basically you need the raw part which includes the Content-Type, Content-Transfer-Encoding and Content-Disposition headers too. The signature includes those headers. If the file you saved does not have those headers in them then you do not have the file that was signed and the signature cannot be verified.

Bob

Hi All,

I am pretty new to Lucene and Pylucene. This is a problem when I am using pylucene to write a customized analyzer, to tokenize text in to bigrams.

The code for analyzer class is:

class BiGramShingleAnalyzer(PythonAnalyzer): def __init__(self, outputUnigrams=False): PythonAnalyzer.__init__(self) self.outputUnigrams = outputUnigrams

def tokenStream(self, field, reader): result = ShingleFilter(LowerCaseTokenizer(Version.LUCENE_35,reader)) result.setOutputUnigrams(self.outputUnigrams) #print ‘result is’, result return result

I used ShingleFilter on the TokenStream produced by LowerCaseTokeinizer. When I call the tokenStream function directly, it works just tine: str = ‘divide this sentence’ bi = BiGramShingleAnalyzer(False) sf = bi.tokenStream(‘f’, StringReader(str)) while sf.incrementToken(): print sf (divide this,startOffset=0,endOffset=11,positionIncrement=1,type=shingle) (this sentence,startOffset=7,endOffset=20,positionIncrement=1,type=shingle)

But when I tried to build a query parser using this analyzer, problem occurred:

parser = QueryParser(Version.LUCENE_35, ‘f’, bi) query = parser.parse(str)

In query there is nothing.

After I add print statement in the tokenStream function, I found when I call parser.parse(str), the print statement in tokenStream actually get called 3 times (3 words in my str variable). It seems to me the parser pre-processed the str I passed to it, and call the tokenStream function on the result of the pre-processing.

Any thoughts on how should I make the analyzer work, so that when I pass it to query parser, the parser could parse a string into bigrams?

Thanks in advance!

Ke Wu

On 04/17/2012 08:05 PM, Camaleón wrote: +1, first follow the instructions precisely, then do any tweaking.

On Sun, Apr 22, 2012 at 10:25 PM, Dom wrote:

Thank you everyone for replying, but unfortunately, nothing seems to work for the moment, although all the answers appear to make sense. First, the array solution appears to work, but when tar gets all the parameters, they become a long string without spaces , obviously “cannot stat: No such file or directory”.

I then tried to add a space char at the BK_LIST increment line, but that didn’t work. Enclosing them in quotes also failed.

Also tried Dom’s suggestion (thank you Dom!) but then, tar won’t be able to stat any file! (and this I actually can’t explain to myself why)

So again, thank you very much for your responses, but the only thing in my mind for the moment is that I really have to go back to the abs-guide (or perhaps find another one?) — bottom line is that there’s so many things I’ve forgot/not used for anything else than to follow a tutorial…

On Sun, Apr 22, 2012 at 04:22:14PM +0300, Andrei POPESCU wrote:

You need to get ahold of the signed part without mutt decoding it. I achieved it by piping the raw message to cat in mutt (“|cat > ~/tmp/foo”) and manually editing the result to cut out the other bits. I needed the particular MIME part for the message, plus the MIME headers above it, and possibly a trailing newline (use trial and error for that bit). You can safely decode/save the signature attachment, it’s just the message itself (which is signed post-encoding, that is, in the “wire” format for the mail) which you need to cut out.

On Sat, Apr 21, 2012 at 05:36:28PM +0100, Sian Mountbatten wrote:

You are conflating backup and filing here. If you are using it for backup, set up a large partition (larger than the source partition) and use something like rdiff-backup, bup or duplicity to back up your source machine(s) onto the disk. Don’t file onto the disk, file on your computer and use the disk for backup.

Or, if you are to use the disc for filing, be aware that it can fail just as an internal disc can.

If you really want to use the drive for both backup and filing (perhaps you have more multimedia than you can fit on your computer’s internal storage), I’d recommend using seperate LVM logical volumes, one purely for backup and the other for files, and still be aware that you haven’t solved the backup issue for the filing partition. (maybe you can burn those to disc and divide up your file storage into directories corresponding to the discs the backups reside on; a tool such as ‘datapacker’ could help you with this)

On 22/04/12 08:34, Cam Hutchison wrote: Or just quote the entries like

BK_LIST=”$BK_LIST “${PARAM}”"

(apologies if thi mail goes through twice, I got a bounce on my earlier attempt)

On Saturday, 21 April, 2012 1:02 Jorge Antonio wrote: From: “Grupo PF_Jorge Antonio Santiago Gonzalez To: “users@httpd.apache.org” Hi,

I am trying to compile the mod_include.c to get the shared object (mod_include.so) and put it in the http.conf, but I get the next error.

Command: # /herramientas/apache_1.3.27/bin/apxs -c mod_include.c && /herramientas/apache_1.3.27/bin/apxs -i -a -n includes mod_include.so

Error: gcc -DSOLARIS2=2100 -DMOD_SSL=208111 -DMOD_PERL -DUSE_PERL_SSI -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUSE_HSREGEX -DEAPI -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC -DSHARED_MODULE -I/herramientas/apache_1.3.27/include  -c mod_include.c mod_include.c:80:20: config.h: No such file or directory mod_include.c:86:35: modules/perl/mod_perl.h: No such file or directory mod_include.c:110: error: syntax error before “MODULE_VAR_EXPORT”

… and so on

Also, I can’t upgrade apache

Server features: SunOS 5.10 Generic_147440-10 sun4u sparc SUNW,SPARC-Enterprise Apache 1.3.27

Thanks for the help.

Regards.

Hello. I found some strange behavour in tomcat 6.0.35 when declaring error-pages in my web.xml. When tomcat picks up an error and redirects it to the location given by the element in , the filters that would have been invoked for that location are actually not invoked.

I found an almost identical report in the bug database: https://issues.apache.org/bugzilla/show_bug.cgi?id=49098 (the user had the same problem when using query strings in ). However, I do not use query strings in my locations and I still get the error.

Is this a bug and is it known? /Ludwig