Description of problem: After yum update, faxmaster receives the error message below via e-mail: FATAL ERROR: /etc/hylafax/setup.cache is missing! Version-Release number of selected component (if applicable): hylafax+.x86_64 7.0.3-1.el6 @epel How reproducible: wait 1 week after yum update Steps to Reproduce: 1. setup /etc and /var on separate devices 2. yum update hylafax 3. Actual results: FATAL ERROR: /etc/hylafax/setup.cache is missing! The file /etc/hylafax/setup.cache is not present. This probably means the machine has not been setup using the faxsetup(8C) command. Read the documentation on setting up HylaFAX before you startup a server system. Expected results: Facsimile transmitted since 08/21/20 03:18: Sender Pages Calls Time Pg/min Errs TypRate TypData -------------------------------------------------------------------- Total 0 0 0:00 0.0 0 Facsimile transmitted in the last seven days: Sender Pages Calls Time Pg/min Errs TypRate TypData -------------------------------------------------------------------- Total 0 0 0:00 0.0 0 Facsimile received since 08/21/20 03:18: Sender CIDName CIDNumber Pages Time Pg/min Errs TypRate TypData <UNSPECIFIED> 1 1:10 0.9 0 12000 2-D MMR ------------------------------------------------------------------------------------------ Total 1 1:10 0.9 0 Facsimile received in the last seven days: Sender CIDName CIDNumber Pages Time Pg/min Errs TypRate TypData ... ------------------------------------------------------------------------------------------ Total 3 2:04 1.5 0 Report failed calls and associated session logs: Nothing to purge in info directory. Truncate merged session logs older than 30 days: Nothing to purge in receive queue. Nothing to purge in the tmp directory. Additional info: [root@frera:/etc] yum history info 376 Loaded plugins: fastestmirror, refresh-packagekit, security Transaction ID : 376 Begin time : Fri Aug 21 13:29:26 2020 Begin rpmdb : 1460:f06cf097933b4c31ee30ce349493df3195b9e67c End time : 13:29:29 2020 (3 seconds) End rpmdb : 1460:c5e910e399d9213d4787fc9a1276d7954c0ef0af User : frera root <root> Return-Code : Success Command Line : -d 2 -y update Transaction performed with: Installed rpm-4.8.0-59.el6.x86_64 @base Installed yum-3.2.29-81.el6.centos.0.1.noarch @updates Installed yum-metadata-parser-1.1.2-16.el6.x86_64 @anaconda-CentOS-201112091719.x86_64/6.2 Installed yum-plugin-fastestmirror-1.1.30-42.el6_10.noarch @updates Packages Altered: Updated hylafax+-7.0.1-1.el6.x86_64 @epel Update 7.0.3-1.el6.x86_64 @epel Updated hylafax+-client-7.0.1-1.el6.x86_64 @epel Update 7.0.3-1.el6.x86_64 @epel Scriptlet output: 1 ln: creating hard link `/etc/hylafax/setup.cache' => `/var/spool/hylafax/etc/setup.cache': Invalid cross-device link 2 ln: creating hard link `/etc/hylafax/setup.modem' => `/var/spool/hylafax/etc/setup.modem': Invalid cross-device link history info -------- Note: problem can be solved by using symbolic links cd /etc/hylafax ln -s /var/spool/hylafax/etc/setup.cache ln -s /var/spool/hylafax/etc/setup.modem
Is the symlink not giving you any trouble for faxrcvd and notify?
The Symlink is working fine. Because hardlinks cannot span separate filesystems, you have two options: - symbolic links - mount --- $ man 2 link .. CONFORMING TO SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES). NOTES Hard links, as created by link(), cannot span file systems. Use sym‐ link(2) if this is required.
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.