![]() |
On Thu, Jun 07, 2001 at 09:08:50PM -0400, Dave Wreski wrote: > > Could you provide a session log from the session which "hung" the > > modem? > > The problem is that hylafax doesn't realize there's a problem, so there's > nothing really quantifiable in the logs: > > Jun 7 15:21:17 fax FaxGetty[1076]: ANSWER: FAX CONNECTION > Jun 7 15:21:52 fax FaxGetty[1076]: RECV FAX (00000368): from 1xxx 796 > 8003, page 1 in 0:18, INF, 3.85 line/mm, 2-D MR, 14400 bit/s > Jun 7 15:22:05 fax FaxGetty[1076]: RECV FAX (00000368): from 1xxx 796 > 8003, page 2 in 0:13, INF, 3.85 line/mm, 2-D MR, 14400 bit/s > Jun 7 15:22:05 fax FaxGetty[1076]: RECV FAX (00000368): > recvq/fax00338.tif from 1xxx 796 8003, route to <unspecified>, 2 pages in > 0:48 > > Then it sat there until about 17:52 when I realized there as a problem (as > per 'faxstat') and reset it. That's the *syslog*. What we need is the *session* log, which I think you'll find in log/00000368, or something similar. Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 804 5015 OS X: Because making Unix user-friendly was easier than debugging Windows ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null