Section 3 : Running a Server

Q355: FIFO Permission problem with faxanswer?

? Got something to say about this answer? Hit the question mark to invoke the mailer and send your comments to the HylaFAQ maintainers.

FIFO Permission problem with faxanswer?

Date: Sat, 5 Oct 1996 07:55:22 +0200 (MST)
From: Matthias Apitz < >
Subject: Re: FIFO Permission problem with faxanswer

Farzin Guilak wrote:
    System configuration:
        HylaFAX 4.0pl0, 
        Solaris 2.5, 
        Telebit Worldblazer Version LA7.02
    I'm having difficulties getting faxanswer to run.  RingsBeforeAnswer
    is set to 0 in my config file, and the hosts file has just the
    default entries.  I don't think I did anything out of the ordinary
    during the installation procedure.
    Whenever I try to run faxanswer, I get the following message
        FIFO: open: Permission denied
    This is regardless of the user (the same message occurs if I run as
    root or as fax).
    I stopped and restarted faxd so it would recreate the FIFOs, and
    they are created with the following permissions:
    # ls -l FIFO*
    prw-------   1 uucp     uucp           0 Oct  3 23:51 FIFO
    prw-------   1 uucp     staff          0 Oct  3 23:51 FIFO.cua_a
    I found the following description in troubleshooting.html, but this
    indicates that the default setup should be correct:
        Processes that want to send faxq information about new modems
        must be able to access the file; this means the protection on
        the file must be such that clients can open it for writing (the
        default setup should make this happen).
    Did I somehow change the default configuration, or is there some
    other parameter that I'm not aware of to cause the FIFOs to have
    different protection?  What *should* the default protection be for
    the FIFOs?
faxanswer belongs to administration commands (1M) and must
be run by root or the faxuser "fax";


 Back to FAQ Index FAQ Index  Next question in List Q356: Start faxserver if reboot? Last updated $Date: 2000/01/10 00:56:31 $.