Gentlemen,
Thank you for your prompt response. I did not subscribe to this topic,
so I am a bit late reacting, sorry. I am happy to see commitment here.
@Giuseppe: I will run faxgetty in the wrapper and get back here with
results. Although I should be able to dig down into the
code as well. The problem occures about once every 2
weeks with a station that does not send ID. Other faxes
we receive without ID are all spam-advertisements.
@Francesco: It sure is a good thing to know the old version works.
I have been running hylafax (with this modem) for over
10 years, so I know it can be as solid as a rock. I can
allow for this situation to continue a bit longer. So
I can contribute to solving this. I'd rather go this
way than to revert back to an old version. I understand
why you would choose for that, though.
@Antonio: I will check, I have been moving the server. But would
you not agree that software should not SEGVIO as a
result of hardware problems?
More information is that the failure seems to occur at the end of the page, not
at the beginning as you'd think from the logging. In the recvq I find a tif
file of a reasonable length for one page.
But there are two things wrong with the file:
It has the wrong rights (rwx------ to user uucp) and when I do chmod 777 the
file still produces no picture. This drives me to the idea that something goes
wrong at the end of the page.
That's all for now. I'll start faxgetty in the wrapper and I'll be back
with the results. Maybe should take a look at the source; I should have
some two weeks before the next failure.
Regards,
Simon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
