Listmates, This is a cross-post to hylafax and openSuSE, rare, but it may implicate an issue with each. I have had a day of hylafax.... I upgraded 4.4 to 6.03 with the src.rpm but then ran into tons of messages in syslog which Aidan on the hylafax list was kind enough to confirm were not really error messages, but very detailed debug messages as if LOG_DEBUG was set. I have checked every hylafax and syslog-ng and yast2-sysconfig settings file and every thing I can find sets: ServerTracing: 1 SessionTracing: 11 As mentioned before I grepped the entire /etc directory with grep -I -ir "fax\|debug\|hyla" and nothing related to fax, log or debug is there. Likewise, there is nothing in any of the yast2-syslog settings that would explain the debug output of hylafax in debug mode. Thinking the generic src.rpm install may be part of the problem, I completely removed hylafax, then built and installed the tarball -- and -- Same Result. (at least we have consistency on our side) From Aidan, one issue (not a show stopper) in hylafax 6.0.3 is "the getaddrinfo calls to get the information about the "hylafax" service are failing. I can't explain why, it works on all the debian/ubuntu/centos installs I have available. But since that's failing, it binds to a hardcoded IPv4 0.0.0.0:4559, which is why youre seeing it "work" yet, despite that error." Hylafax 6.0.3 does work on 10.3, but with 60+ log entries a minute, the logs fill up fast. What I need from the openSuSE list is how to turn off the LOG_DEBUG syslog behavior if it is in fact a syslog configuration issue from a past hylafax rpm install that is causing the debug level logging. Additionally, if anybody has any ideas why the getaddrinfo call is failing, we can probably solve the suse/new hylafax issue and get the latest hylafax version debugged for 11.2 as well. What I need from the hylafax folks is also how to turn ServerTracing back to level 1 so I can eliminate the thousands of log entries if possible. If the debug level logging is somehow cause by the failing getaddrinfo call tripping debug level logging, then I guess I need to know if that in it self is a bug I need to report to hylafax. My hylafax config files (both class1 and class2.0 can be found at: http://www.3111skyline.com/download/linux/apps/hylafax/config/ The log messages associated with the start-up and shutdown of hylafax are at: http://www.3111skyline.com/download/linux/apps/hylafax/syslog.msgs everything after the "Parsing hostPort(): "EPRT" " line just repeats in blocks of 20-30 entries every 30 seconds or so after startup. On shutdown, hylafax does offer a clue concerning the debug situation. Evidenly FaxQuerer thinks it is in debug mode. The following are the shutdown messages received: Aug 19 23:38:06 nirvana FaxQueuer[20744]: QUIT Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: Listing destJobs with 0 items Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: runq(0x636cd8) next 0x636cd8 Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: batchq(0x636d08) next 0x636d08 Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: destq(0x636cf0) next 0x636cf0 Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: pendq(0x636d68) next 0x636d68 Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: suspendq(0x636d38) next 0x636d38 Aug 19 23:38:06 nirvana FaxQueuer[20744]: DEBUG: inSchedule: NO hopefully that points us in the right direction This is on a test box, so I'm not in any big hurry, but I would like to figure out what is going on so we can sort this out. Let me know if there is anything else I can post or any other tests I can run that might help and I'll be happy to do it. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org