The PR wasn't quite right with regards to stage support, so I had to modify
it further. The post-install configure file handling was focused on the
wrong file. I updated the default name of the qpage configure file in
order to use the @sample keyword. I added an entry in UPDATING to let
users know they may need to move an existing configure file accordingly.
Submitted by: maintainer (Jeff Blank)
Changes by: marino
Nitpicks for the comms/qpage port
The comms/qpage port has a few minor problems. A default installation
the following errors when the /usr/local/etc/rc.d/qpage.sh script is
qpage: cannot open /etc/qpage.cf: No such file or directory
qpage: cannot access LockDir(/var/spool/lock): Permission
qpage: cannot access QueueDir(/var/spool/qpage): No such file
qpage: cannot chdir to QueueDir(/var/spool/qpage): No such
file or directory
1) qpage looks for its configuration file in /etc instead of
2) It setuid()'s to a user (daemon) without permission to access
but does not document this anywhere outside of the source.
3) It's queue directory is not created by installing the port.
Submitted by: Kirk Strauser <firstname.lastname@example.org>