+-----------------------------------------------------------------------
| Running hylafax on OpenBSD
+-----------------------------------------------------------------------

Post-installation steps
=======================
Hylafax needs some manual configuration before it is usable.

If you have upgraded HylaFAX on a system which was using the legacy UUCP
account, please see the section below to update ownership of files.

Make sure that you have configured HylaFAX before running faxq:
	server: /usr/local/sbin/faxsetup
	modems: /usr/local/sbin/faxaddmodem
	incoming calls: /etc/ttys

When you are asked to specify the name of tty device, use a tty device
existing on your architecture instead of "ttyd1".

For accepting incoming FAX/data calls, modify /etc/ttys(5) to contain
something like this:

    tty00	"/usr/local/sbin/faxgetty"	dialup	on

and send a SIGHUP to init(8).


Updating HylaFAX+ fontmap file
==============================
To refresh or create a missing HylaFAX fontmap file after an update simply run;

    # /usr/local/sbin/faxsetup -client


Updating file ownership to use the new _hylafax account
=======================================================
Old versions (6.x) of this package used the legacy UUCP account. This was
changed to _hylafax when moving to 7.x. If your HylaFAX spool directory
still contains files owned by _uucp / uid 66, update the ownership as follows.

If the legacy UUCP account is still registered;

    find /usr/local/libdata/hylafax -user uucp -exec /sbin/chown 902 {} \;
or
    find /usr/local/libdata/hylafax -user uucp -exec /sbin/chown _hylafax {} \;

Alternatively, if you have removed the legacy UUCP account, and assuming its uid
was 66;

    find /usr/local/libdata/hylafax -user 66 -exec /sbin/chown _hylafax {} \;


References
==========
Additional documentation at https://hylafax.sourceforge.io/.
