Re: [hylafax-users] Debian sarge- Hylafax 4.2 - Kde clients

[Christian Lauinger <clauinger@xxxxxxxxxxxxxxxx>]

Bodo Meissner schrieb:
> Am 2004.11.08 12:20 schrieb(en) Christian Lauinger:
>
> > This is in my syslog:
> > Nov  8 11:12:21 conop01 FaxSend[27241]: /dev/faxCAPI: Can not open  
> > modem (No such file or directory)
> > Nov  8 11:12:51 conop01 FaxSend[27241]: /dev/faxCAPI: Can not open  
> > modem (No such file or directory)
> > Nov  8 11:12:51 conop01 FaxSend[27241]: Unable to setup modem on / 
> > dev/faxCAPI; giving up after 2 attempts
> > Nov  8 11:12:51 conop01 FaxQueuer[20711]: MODEM /dev/faxCAPI appears  
> > to be wedged
> > Nov  8 11:12:51 conop01 FaxQueuer[20711]: MODEM WEDGED: bin/wedged  
> > "faxCAPI" "/dev/faxCAPI"
>
>
> Hello Christian,
>
> probably you have a faxgetty running which tries to initialize a modem  
> on /dev/faxCAPI. (There might be other log messages complaining about  
> syntax errors in config.faxCAPI because the format used ba capi4hylafax  
> is differnt from Hylafax' normal config file format.)

Hello Bodo,

you are right, I found this in the log:
Nov  8 16:41:37 conop01 HylaFAX[31236]: Filesystem has SysV-style file 
creation semantics.
Nov  8 16:41:37 conop01 FaxQueuer[20711]: SUBMIT JOB 16
Nov  8 16:41:40 conop01 FaxSend[31242]: Syntax error at line 149, 
missing ':' in "{"
Nov  8 16:41:40 conop01 FaxSend[31242]: Syntax error at line 289, 
missing ':' in "    {"
Nov  8 16:41:40 conop01 FaxSend[31242]: Syntax error at line 394, 
missing ':' in "    }"
Nov  8 16:41:40 conop01 FaxSend[31242]: Syntax error at line 395, 
missing ':' in "}"
Nov  8 16:41:40 conop01 FaxSend[31242]: /dev/faxCAPI: Can not open modem 
(No such file or directory)

> Faxgetty can be started by init as configured in /etc/inittab or by a  
> hylafax startup script.
> If you have entries in /etc/inittab which start faxgetty, remove these  
> and call "init q".
Nothing found in inittab
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:3:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let 
this work."

# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

#-- isdnutils begin
# Change the line below for your local requirements and uncomment them.
# Use "init q" to reread inittab.
# look at the mgetty manpage for more information (mgetty isn't standard!)
#
#I0:2345:respawn:/sbin/mgetty -D -m '"" ATZ OK AT&Eyourmsnhere OK 
AT&B512 OK' -s 38400 ttyI0
#-- isdnutils end

Think this is OK ?
> On Debian, change /etc/default/hylafax to set "USE_FAXGETTY=no" and  
> restart hylafax-server. (This prevents the startup script from starting  
> faxgetty.)
Checked and value was "no".
> > Nov  8 11:13:08 conop01 HylaFAX[27259]: nss_ldap: could not connect  
> > to any LDAP server as (null) - Can't contact LDAP server
>
>
> Don't know what this means.
Me too :D
> Bodo

Christian


____________________ 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*