![]() |
At 01:21 AM 5/17/00 +0200, Stephan Bauer wrote: >With the new hylafax-4.1beta2 it shows only: > >May 17 00:40:49.92: [ 4093]: --> [2:OK] >May 17 00:40:49.94: [ 4093]: DIAL 082221039 >May 17 00:40:49.94: [ 4093]: <-- [16:ATDT0082221039@\r] >May 17 00:41:31.51: [ 4093]: --> [4:+FCO] >May 17 00:41:34.38: [ 4093]: --> [128:+FNF: 00 00 09 12 09 4D 30 30 30 >30 31 32 33 34 35 36 37 38 49 82 22 10 39 FF FF FF FF FF FF FF 01 0B 02 >02 10 01 82 0E 00 00 09] > >Than the log stops and in /var/log/messages there ist the following >entry: > >May 17 00:40:45 supernase FaxSend[4093]: SEND FAX: JOB 3 DEST 082221039 >COMMID 00000003 >May 17 00:41:34 supernase FaxQueuer[806]: JOB 3: Send program terminated >abnormally with exit status 0xb Ack! it looks like the NSF patches i committed a few days ago. Do you get a core dump - if so could you look at it with gdb or similar to find the problem location. I think if this is for linux 0xb is a segmentation violation. >When I send a fax to a fax machine the log says that ist is a HP fax but >it isn't one: > >May 17 00:45:21.40: [ 4137]: --> [29:+FNF: AD 00 36 40 80 28 01 E4] >May 17 00:45:21.40: [ 4137]: REMOTE NSF " AD 00 36 40 80 28 01 E4" >May 17 00:45:21.40: [ 4137]: NSF remote fax equipment: HP >May 17 00:45:21.40: [ 4137]: --> [27:+FCI:" "] Hmmm that is not good either - but i think the first problem is worse. :-( - Robert