[hylafax-users] problem with faxgetty and debian

[csaunders <csaunders@databytesoftware.com>]

Hi all,

I have a problem with faxgetty (please see complete system details below) 
where upon no matter what i do i can't get it to work properly. my console 
has tons of "respawning" too fast msgs, and judging by the archives this is 
common ground. the problem is that i have spent over 6 hours ploughing 
through the archives and not one of the suggested solutions work. if anyone 
can suggest the next step to take or even an answer to my woes i would be 
extremly gratefull.

summary :
* the problem : fax getty won't run (ie ps -ef doesn't show up fax gettty) 
either from the command line or from the init scripts.

* if i use a different modem it appears to be fine, ie it will make the 
vt100 term wait until i ctrl-c to kill it from the command line (i havent 
tested it with the different modem in the inittab) i don't want hylafax to 
touch the first modem, just the second. will the lock thats almost always 
exists on the first modem upset hylafax (faxgetty)? is there a way to 
ensure hylafax (faxgetty) only uses the second modem?

* the intended modem works (i used minicom and dialed out successfully with 
it) but i've only recently attached it to /dev/ttyS1 so it doesn't have any 
data stuff working with it. i am running my data stuff on /dev/ttyS0 so 
hylafax can have /dev/ttyS1 all to itself.

* there are no locks against /dev/ttyS1 (no releveant files in /var/lock) 
and definatly no software configured for usage on the port (though i 
wouldn't be suprised if something is checking it and screwing stuff up, i 
just wouldn't know how to detect it)

* the rights for the device are the same as the working device /dev/ttyS0 
being : owner root, group dialout, and +c +r +w for root (no rights for any 
other user or group). These are possibly wrong but i don't know what the 
rights should be for the device. i did set 777 on ttyS1 but it made no diff 
i think.

* there appears to be no related messages in /var/log/messages relating to 
the faxgetty problem (there is nothing in the /var/log/hylafax directory)

* my inittab script reads "S1:23:respawn:/usr/sbin/faxgetty /dev/ttyS1" 
which is the correct paths for both device and faxgetty

* i used addmodem to setup the device and it appears to have excuted 
correctly, i get the attached config.ttyS1 file (see below)

* the hylafax debian package i installed was from debian.org being ver : 
(not sure, how do i tell?) either v 4.0.2.-14 or the 41beta2-2

* the debian version i am running is : 2.2.6 (base system)

* the modem i am using is : us robotics sportster voice 56K fax modem 
external

<attached config.ttys1 file residing in both 
/var/spool/fax/etc/config.ttyS1 and /etc/hlyafax/config.ttyS1>
************************************************************************

# $Id: usr-2.0,v 1.6 2001/06/04 05:09:46 darren Exp $
#
# HylaFAX Facsimile Software
#
# Copyright (c) 1990-1996 Sam Leffler
# Copyright (c) 1991-1996 Silicon Graphics, Inc.
# HylaFAX is a trademark of Silicon Graphics, Inc.
#
# Permission to use, copy, modify, distribute, and sell this software and
# its documentation for any purpose is hereby granted without fee, provided
# that (i) the above copyright notices and this permission notice appear in
# all copies of the software and related documentation, and (ii) the names 
of
# Sam Leffler and Silicon Graphics may not be used in any advertising or
# publicity relating to the software without the specific, prior written
# permission of Sam Leffler and Silicon Graphics.
#
# THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
# EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
# WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
#
# IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
# ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
# OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
# WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
# LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
# OF THIS SOFTWARE.
#

#
# Configuration for using the Class 2.0 command interface
# with a USR v.34 Courier or Sporster modem.
#
# RTS/CTS flow control is used default.
#
#
CountryCode:            64
AreaCode:               9
FAXNumber:              +64.9.534.5010
LongDistancePrefix:     0
InternationalPrefix:    00
DialStringRules:        etc/dialrules
ServerTracing:          1
SessionTracing:         0x08501
RecvFileMode:           0640
LogFileMode:            0640
DeviceMode:             0660
RingsBeforeAnswer:      0
SpeakerVolume:          off
GettyArgs:              "-r -b %l"
LocalIdentifier:        "NothingSetup"
LogFacility:            daemon
TagLineFormat:          "From %%l|%c|Page %%P of %%T"
MaxRecvPages:           25
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType:              Class2.0        # use class 2.0 interface
ModemRate:              38400           # DCE-DTE communication rate
ModemFlowControl:       rtscts          # XON/XOFF flow control assumed
#
ModemNoFlowCmd:         AT&H0&I0&R1     # setup modem for no flow control
ModemHardFlowCmd:       AT&H1&I0&R2     # setup modem for hardware flow 
control
ModemSoftFlowCmd:       AT&H2&I2&R1     # setup modem for software flow 
control
#
ModemSetupDTRCmd:       ATS13=1&D2      # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or 
not)
ModemResultCodesCmd:    ATQ0X4          # enable extended result codes
#
# NB: adaptive answer only seems to work properly when
#     the modem is left idling in Class 2.0
#
ModemSetupAACmd:        AT+FAA=1
#
# Set modem speaker volume commands: OFF QUIET LOW MEDIUM HIGH.
# Note that we both turn the speaker on/off and set volume.
#
ModemSetVolumeCmd:      "ATM0 ATM1 ATM1 ATM1 ATM1"
#
# Modem does not support HDLC frame tracing; we add this just
# to eliminate spurious ERROR results that confuse the naive.
#
Class2BUGCmd:           AT+FBU=0
#
# The modem doesn't support copy quality checking, even though it
# returns (0-2,0-2) for AT+FCQ=?; therefore we override the query
# response so that the server will do copy quality checking.
#
Class2CQQueryCmd:       !(0),(0)        # override modem response
#
# Disables the reporting of bad frames by the modem.  This
# overcomes a firmware problem in the x2 and V90 Sportsters.
# It is not necessary for the Courier modem.
#
Class2NRCmd:    AT+FNR=1,1,1,0
#
# USR modems violate Class 2.0 specs and do not send RTC itself
#
Class2SendRTC:  yes
#
# +FAP=? not supported on this modem, gives ERROR in ServerTracing
#
Class2APQueryCmd:       none
************************************************************************


cs

Kind Regards

Colin Saunders
Director
DataByte Software Ltd
************************************************************************
Ph : 025 290 5093 Fax : 08 326 4187 Email : csaunders@databytesoftware.com
DataByte Software Ltd, P O Box 98817, S.A.M.C, AUCKLAND, New Zealand




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null