Bug 63843 - Error in sample script new_fax.tiff
Summary: Error in sample script new_fax.tiff
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mgetty
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-19 12:06 UTC by Terje Trane
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-04 20:12:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Terje Trane 2002-04-19 12:06:47 UTC
Description of Problem:

There two errors in the contributed sample script /usr/doc/mgetty-
1.1.25/samples/new_fax.tiff. The line 

    FAX=`echo $1|sed 's/...$//'`  

should have the $1 changed to $4. (This is supposed to be the filename without 
the page number: .01, .02 ....)

The line 

    metasend -b -F "Fax Getty <root>" -f /tmp/$FAX_BASENAME.tiff \
      -m image/tiff -s "fax from $SENDER" -S 4000000 -t $MAILTO  

has a space after the backslash that shouln't be there. (The backslash does not 
work as supposed unless it is the very last character before the newline.)

Also, if the 

    MAILTO="Faxverteiler <fax>" 

could be replaced with

    MAILTO="faxadmin"
 
it will work right away for all that sets up /etc/aliases as suggested in the 
docs.


Version-Release number of selected component (if applicable):

mgetty-1.1.25-4.6.i386.rpm in RH6.2 updates (also mgetty-1.1.21-4.i386.rpm in 
original RH6.2)

Comment 1 Jason Vas Dias 2005-08-01 22:31:35 UTC
Sorry for the long delay in processing this bug report. It got mislaid somehow.
This is now fixed in Rawhide (mgetty-1.1.33-4_FC5).



Comment 2 Bill Nottingham 2006-08-04 20:12:07 UTC
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.


Note You need to log in before you can comment on or make changes to this bug.