HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] sendq/doneq Description Permissions
Why not crontab a perl script, that will run every 60 seconds as UUCP and
extract the info you need from the 'queue' dirs? You can then dump it into a
raw text or HTML file in your web directory. You can chmod the work file,
after you're done updating it, to make sure it's world readable. The queue
file format will be a breeze to split() using perl. You can also have it
build a long-life stats file if you want, for later analysis of all faxes
ever sent.
Now that I think about it, I'm going to do that right now for my server. :P
Glen
-----Original Message-----
From: hylafax-users-bounce@xxxxxxxxxxx
[mailto:hylafax-users-bounce@xxxxxxxxxxx]On Behalf Of Richard Morris
Sent: Thursday, June 10, 2004 6:28 PM
To: hylafax-users@xxxxxxxxxxx
Subject: [hylafax-users] sendq/doneq Description Permissions
Hello all,
I was wondering if someone could help me. I am building a web interface for
our HylaFax server and I would like to pull the details from the description
files located in the sendq/doneq directories. However, the files are
written by the uucp user and only have read access for the owner and group.
Unfortunately the web server doesn't have permission to read those files in
this case. I tried changing the configuration file and setting the
RecvFileMode, LogFileMode, DeviceMode and UUCPLockMode options to 0664 but
every time one of the sendq/doneq files were created it was still with the
old permissions.
Is there a way to set the permissions to allow read access by everyone on
the description files in the sendq/doneq directories? Thanks.
Richard
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*