The comms/qpage port has a few minor problems. A default installation gives
the following errors when the /usr/local/etc/rc.d/qpage.sh script is
execute:
qpage[68438]: cannot open /etc/qpage.cf: No such file or directory
qpage[68438]: cannot access LockDir(/var/spool/lock): Permission denied
qpage[68438]: cannot access QueueDir(/var/spool/qpage): No such file or directory
qpage[68438]: cannot chdir to QueueDir(/var/spool/qpage): No such file or directory
In short:
1) qpage looks for its configuration file in /etc instead of /usr/local/etc
2) It setuid()'s to a user (daemon) without permission to access /var/spool/lock
but does not document this anywhere outside of the source.
3) It's queue directory is not created by installing the port.
PR: ports/48059
Submitted by: Kirk Strauser <kirk@strauser.com>
options `start' and `stop' now (unless I have forgotten any). This allows
us to call the scripts from /etc/rc.shutdown with the correct option.
The (42 or so) ports that already DTRT before are unchanged.
HTTP/1.1 request. Moved distfile to www.freebsd.org/~fenner/
temporarily. Left original MASTER_SITE commented out - newer
fetch fetches the distfile properly, and server administrator is
working on the problem, so will probably be able to be moved back
soon.
-------
===> Extracting for qpage-3.2
>> Checksum OK for qpage-3.2.tar.Z.
/usr/bin/tar: archive /usr/ports/distfiles//qpage-3.2.tar.Z EOF not on block boundary
*** Error code 1
Stop.
# make package
>> qpage-3.2.tar.Z doesn't seem to exist on this system.
>> Attempting to fetch from http://www.qpage.org/download/.
Receiving qpage-3.2.tar.Z (149352 bytes): 100%
149357 bytes transfered in 24.5 seconds (5.95 Kbytes/s)
>> Checksum mismatch for qpage-3.2.tar.Z.
Make sure the Makefile and md5 file (/usr/ports/BROKEN/comms/qpage/files/md5)
are up to date. If you want to override this check, type
"make NO_CHECKSUM=yes [other args]".
*** Error code 1
Stop.
#
the import message used when it was imported to ports/misc:
New port, qpage:
QuickPage sends messages to a paging terminal using the SNPP and IXO
(also known as TAP) protocols. It is normally used with no options
other than a recipient and the message text, in which case the message
is sent to the SNPP server where it is submitted to a page queue to be
sent by a separate daemon process.
PR: 4224
Submitted by: Joe Stein <joes@seaport.net>
