HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] faxCAPI
Bodo Meissner wrote:
Am 2004.11.02 15:37 schrieb(en) Dominik Bethke:
Bodo Meissner wrote:
what messages from hylafax do you get in syslog?
Every log in my system tells me that the Capi is OK
Hello Dominik,
I don't think anyone can help you if you only "summarize" the log
messages like this.
When you start Hylafax you probably get some syslog messages. (On my
Debian system they are in /var/log/messages.) You will get more
messages if you change ServerTracing in your hylafax config file.
If you don't find a problem in these messages, maybe someone else
will see what's going wrong. Please, show the log messages.
There might be useful messages in
/var/spool/hylafax/logs/capi4hylafax as well.
Bodo
____________________ HylaFAX(tm) Users Mailing List
_______________________
To subscribe/unsubscribe, click
http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx <
/dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
My log says:
Nov 2 16:08:29 faxserver FaxQueuer[12605]: MODEM /dev/faxCAPI appears
to be wedged
Nov 2 16:08:29 faxserver FaxQueuer[12605]: MODEM WEDGED: bin/wedged
"faxCAPI" "/dev/faxCAPI"
but I do not have a capi4hylafax log,but there is a capisuite.error that
says
Mon Nov 1 11:21:23 2004 CapiSuite 0xbffff560: CapiSuite 0.4.3 started.
Hope that you can help me
Thanks
--
Mit freundlichen Grüßen
Dominik Bethke
(Trainee Technical Support Engineer)
Juwi MacMillan Group GmbH
Bockhorn Nr. 1
D-29664 Walsrode
T. +49 5162 98 15 60 69
F. +49 5162 98 15 29 39
E. dominik.bethke@xxxxxxxxxx
www.juwimm.com
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*