On Tue, Feb 08, 2005 at 10:38:02AM +0100, Giuseppe Sacco wrote:
>
> Please, check if running 'faxsetup -server' fixes the problem. And see
> the differences to /etc/hylafax/setup.cache
>
>
That didn't seem to help. I got the same notification of attempted
email delivery without a recipient.
I also encountered a number of other warnings or problems that might
indicate faxsetup -server isn't totally integrated into Debian. In
particular, everything was not running when it finished. I did a
manual /etc/init.d/hylafax restart to get the fax delivery attempted.
I run faxgetty from inittab.
Also, as noted at the bottom, faxalter -d doesn't seem to be working.
Here's my log as root; it include a diff of setup.cache:
-----------------------------------------------------------
wheat:/usr/local/rootlog# date
Tue Feb 8 14:23:04 PST 2005
wheat:/usr/local/rootlog# cp /etc/hylafax/setup.cache
/etc/hylafax/setup.cache.old
wheat:/usr/local/rootlog# faxsetup -server
Setup program for HylaFAX (tm) 4.2.1.
Created for i686-pc-linux-gnu on Tue Jan 11 21:40:51 UTC 2005.
Reading cached parameters from /var/spool/hylafax/etc/setup.cache.
Found encoder: /usr/bin/uuencode
Looks like /usr/bin/base64-encode supports base64 encoding.
Checking system for proper server configuration.
Warning: /etc/hylafax/getty-link does not exist or is not an executable program!
The file:
/etc/hylafax/getty-link
does not exist or this file is not an executable program. The
HylaFAX software optionally uses this program and the fact that
it does not exist on the system is not a fatal error. If the
program resides in a different location and you do not want to
install a symbolic link for /etc/hylafax/getty-link that points to your program
then you must reconfigure and rebuild HylaFAX from source code.
Warning: /etc/hylafax/vgetty-link does not exist or is not an executable
program!
The file:
/etc/hylafax/vgetty-link
does not exist or this file is not an executable program. The
HylaFAX software optionally uses this program and the fact that
it does not exist on the system is not a fatal error. If the
program resides in a different location and you do not want to
install a symbolic link for /etc/hylafax/vgetty-link that points to your program
then you must reconfigure and rebuild HylaFAX from source code.
Warning: /etc/hylafax/egetty-link does not exist or is not an executable
program!
The file:
/etc/hylafax/egetty-link
does not exist or this file is not an executable program. The
HylaFAX software optionally uses this program and the fact that
it does not exist on the system is not a fatal error. If the
program resides in a different location and you do not want to
install a symbolic link for /etc/hylafax/egetty-link that points to your program
then you must reconfigure and rebuild HylaFAX from source code.
Make /var/spool/hylafax/bin/ps2fax a link to /var/spool/hylafax/bin/ps2fax.gs.
Make /var/spool/hylafax/bin/pdf2fax a link to /var/spool/hylafax/bin/pdf2fax.gs.
Update /var/spool/hylafax/status/any.info.
HylaFAX configuration parameters are:
[1] Init script starts faxq: 1
[2] Init script starts hfaxd 1
[3] Start old protocol: no
[4] Start paging protocol: no
Are these ok [yes]?
Modem support functions written to /var/spool/hylafax/etc/setup.modem.
Configuration parameters written to /var/spool/hylafax/etc/setup.cache.
Restarting HylaFAX server processes.
You have a HylaFAX scheduler process running. faxq will be
restarted shortly, as soon as some other work has been completed.
Can I terminate this faxq process (1114) [yes]?
Should I restart the HylaFAX server processes [yes]?
/etc/init.d/hylafax start
Not starting HylaFAX daemons since they are already running.
Looks like you have some faxgetty processes running (PIDs are):
1605
It is usually a good idea to restart these processes after running
faxsetup; especially if have just installed new software. If these
processes are being started by init(8) then sending each of them a
QUIT message with the faxquit command should cause them to be restarted.
Is it ok to send a QUIT command to each process [yes]?
/usr/sbin/faxquit ttyS0
Done verifying system setup.
Creating /etc/hylafax/config.sav from /var/spool/hylafax/config.sav.
Updating /etc/hylafax/setup.cache from /var/spool/hylafax/setup.cache.
Updating /etc/hylafax/setup.modem from /var/spool/hylafax/setup.modem.
wheat:/usr/local/rootlog# diff /etc/hylafax/setup.cache.old
/etc/hylafax/setup.cache
2c2
< # on Thu Jun 27 14:50:12 PDT 2002 for root
---
> # on Tue Feb 8 14:24:52 PST 2005 for root
10c10
< DPSRIP='/usr/sbin/ps2fax.exe'
---
> DPSRIP='/usr/local/sbin/ps2fax.exe'
11a12
> ENCODING='base64'
13c14
<
FONTPATH='/usr/local/lib/ghostscript/common:/usr/local/lib/ghostscript/6.53:/usr/local/lib/ghostscript/fonts:/usr/local/share/ghostscript/common:/usr/local/share/ghostscript/6.53:/usr/local/share/ghostscript/fonts:/var/lib/defoma/gs.d/dirs/fonts:/usr/share/ghostscript/common:/usr/share/gs/6.53'
---
> FONTPATH='/usr/share/enscript/afm:/usr/share/fonts/afms/adobe:/usr/share/fonts/type1/gsfonts'
24c25,26
< MANDIR='/usr/local/man'
---
> MANDIR='/usr/share/man'
> MIMENCODE='/usr/bin/base64-encode'
40a43
> TTYCMD='/usr/bin/tty'
42a46
> UUENCODE='/usr/bin/uuencode'
# time passed as I tried to send the fax.
# initially I was online, so the modem was not available.
# Even when I went offline, nothing happened,
# even with faxalter -p xxx
# I noticed that faxstat -s reported the Hylafax scheduler
# was not running. So I did the following:
wheat:/usr/local/rootlog# /etc/init.d/hylafax restart
Stopping HylaFAX daemons: faxq(not running) hfaxd.
Starting HylaFAX daemons: faxq hfaxd.
# then the fax transmitted.
----------------------------------------------------------------
In the diff above, I notice some references to /usr/local, which seems
like an error. Some of them are in the old file, and some are in the
new file! (e.g., it was /usr/local/man; new one refers to
/usr/local/sbin/ps2fax.exe).
For now I am reverting to the previous setup.cache (I'm particularly
concerned about the font paths).
Hmm... could the copying between /etc/ and /var/spool/hylafax/etc have
caused the newer setup.cache not to take?
Final issue: I attempted to modify the destination with
faxalter -d "[EMAIL PROTECTED]" 140
and then
faxalter -d 5501062 140
(both run from the account from which I submitted the job).
but neither of these seem to have had an effect. faxstat -s reported
the same destination before and after them, and the fax that finally
went out seems to have used the original phone number.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
