196147 2007-10-17 09:38 0000 net-misc/hylafax not using mgetty for data connections when USE="mgetty" 2007-10-17 21:20:22 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All Linux RESOLVED FIXED P2 normal --- 1 makoomba@gmail.com nerdboy@gentoo.org makoomba@gmail.com 2007-10-17 09:38:56 0000 when hylafax is compiled with USE="mgetty", faxgetty should use /sbin/mgetty for data incoming calls (instead of agetty) fix: hylafax ebuild should set --with-PATH_GETTY=/sbin/mgetty Reproducible: Always jakub@gentoo.org 2007-10-17 09:41:31 0000 Uhm? What's your trouble? <snip> if use mgetty; then my_conf="${my_conf} \ --with-PATH_EGETTY=/sbin/mgetty \ --with-PATH_VGETTY=/usr/sbin/vgetty" else my_conf="${my_conf} \ --with-PATH_EGETTY=/bin/false \ --with-PATH_VGETTY=/bin/false" fi </snip> makoomba@gmail.com 2007-10-17 10:26:33 0000 (In reply to comment #1) > Uhm? What's your trouble? in my setup, i have a class 2.0 modem configured with adaptive answer. for this to work, i have to use GettyArgs, otherwise Data connections whould be refused: <snip from faxGettyApp.c++> traceServer("ANSWER: DATA CONNECTION"); if (gettyArgs != "") { sendModemStatus("d"); runGetty("GETTY", OSnewGetty, gettyArgs, emsg, lockDataCalls, callid); sendModemStatus("e"); } else traceServer("ANSWER: Data connections are not permitted"); </snip> since <snip> /* * The pathnames of the getty, vgetty, and egetty programs * invoked by faxgetty to handle inbound data and voice * calls and for doing adaptive call type deduction. These * parameters are compiled into the binary to avoid possible * security problems. */ </snip> if you don't set --with-PATH_GETTY=/sbin/mgetty, PATH_GETTY whould be hardcoded to /sbin/agetty nerdboy@gentoo.org 2007-10-17 21:20:22 0000 Fixed in portage...