El 2024-09-01 a las 17:48 +0200, Giuseppe Sacco escribió: > Hi, > > Il giorno dom, 01/09/2024 alle 17.15 +0200, Camaleón ha scritto: > [...] > > As I pointed out in my first comment on this bug, I set the > > variables in «/etc/hylafax/hfaxd.conf.systemd» and gave them a «null» > > (empty) value as instructed in README file: > > > > root@stt005:/var/spool# cat /etc/hylafax/hfaxd.systemd.conf | grep -i faxq > > FAXQCLEAN_OPTS="" > > FAXQCRON_OPTS="" > > > > In the meantime, how can I safely disable ANY cronjob related to > > HylaFAX? > > hylafax is composed of two daemons, hfaxd is responsible for receiving fax > requests from client machines; faxq is responsible for scheduling and sending > all outgoing faxes. These are the main hylafax systemd services. > > Then, you configure faxgetty for all your modems in order to be able to > receive faxes. These are systemd services as well. > > Beside systemd services, there is a periodic script ran by cron. It uses > faxqclean in order to remove old faxes (images), and faxcron for removing > logs. These two commands are ran via cron and via /etc/cron.weekly/hylafax. > > So, the configuration file /etc/hylafax/hfaxd.conf.systemd contains > information about the server ip addresses, the TCP port numbers, the protocol > to use. It does not run periodic cleaning and does not use FAXQ* variables.
Ummm... I see. > /etc/cron.weekly/hylafax is just a normal shell script. In order to avoid its > execution, you may just add "exit 0" as second line. This script sources > /etc/default/hylafax in order to fetch FAXQ* variables, and provide default > values if these are not set in the configuration file. > > The /usr/share/doc/hylafax-server/README.Debian.gz also suggest, in order to > block the cron script, to set both variables as empty: > FAXQCLEAN_OPTS="" > FAXCRON_OPTS="" > > Could you check if this solve the problem? So, if the two variables have to be set at «/etc/default/hylafax», as defined by weekly cronjob, the file should be created by default as it used to be in older Debian versions or at least it should be noticed in README and/or NEWS becasue is a BIT confusing as it is now :-? Ok. I will manually create /etc/default/hylafax file, set the variables in there, fully restore faxes and files from backup, restart services, test and pray. Will report/update here the next week about this issue. Thanks! -- Camaleón
