Adventures in building and using yafu

[bsquared]

Originally Posted by James Heinrich

One last question: if I now seem to be reading yafu.ini correctly by cd'ing to the directory first, would this be the correct format to disable (session|factor).log and avoid those parameters?
session="/dev/null"
logfile="/dev/null"

Glad we found something that works. You should not need the quotes around if those lines are in the .ini file, otherwise yes, that should work.
session=/dev/null
logfile=/dev/null

[James Heinrich]

Originally Posted by bsquared

You should not need the quotes around if those lines are in the .ini file, otherwise yes, that should work.

I was just copying the commented-out example (e.g. session="session.log")

Thanks for your help, as always.

[bsquared]

Originally Posted by James Heinrich

I was just copying the commented-out example (e.g. session="session.log")

Thanks for your help, as always.

The example was apparently wrong in the file

Thanks for the reports!

It appears that this thread is actually all about the adventures of building and using yafu; very little to do with msieve outside the first few posts. So unless there are objections I will move the thread into the yafu subforum and rename.

[James Heinrich]

Yes, please rename and move as appropriate.

Hmm, just when I thought I was getting somewhere:

sh: line 1: 1841007 Done echo '42314127400940'
1841008 Segmentation fault (core dumped) | ./yafu
sh: line 1: 1841013 Done echo '42314127400940'
1841014 Segmentation fault (core dumped) | ./yafu

Fortunately I have an alternate codepath using PARI/GP that does the same thing (and it always works), so it isn't super-critical that I get this working, but it would be nice. Pain to debug though -- it works when you test it, and fails when you use it.

[bsquared]

Originally Posted by James Heinrich

Yes, please rename and move as appropriate.

Hmm, just when I thought I was getting somewhere:
Fortunately I have an alternate codepath using PARI/GP that does the same thing (and it always works), so it isn't super-critical that I get this working, but it would be nice. Pain to debug though -- it works when you test it, and fails when you use it.

Can't get that one to fail for me, so far. I take it that it works except when used in your script?

[James Heinrich]

I have no idea what's going on here. Obviously it was trying to factor (k in new factor of M212223871), would have been called as:
cd /var/www/vhosts/mersenne.ca/yafu/yafu && echo '42314127400940' | ./yafu

That command works fine from the shell. Works fine run inside a script run manually. Works fine inside a test script run under the web user.
And yet, when called in a production script, segfault? I'm not even certain from that message if it's yafu that's dying (but what else?)

If I can't replicate the failure, I don't expect you to be able to.

[LaurV]

Originally Posted by bsquared

Interesting and irrelevant side-note, when testing this out, I randomly typed in a 16-digit prime number:
echo "1703948751903457" | ./yafu

You are logarithmically lucky today!