|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
trouble with hosts-file
<x-html><HTML>
Hello everybody,
<P>I've big problems with the hosts-file from HylaFax.
<BR>I've added the users, which should have access-rights to the fax-server
like this:
<P><B>root@127.0.0.1:::XXXXXXXX</B><B></B>
<P>where XXXXXXX is the encrypted password like mentioned in /etc/shadow
<BR>Then I've changed the file to mode 600, owned by User fax from the
group uucp.
<BR>User fax and Group uucp have the same uid 14.
<P>But everytime when I want to do "<B>faxstat -srv</B>" (or i.e. sendfax
or something like this),
<BR>I get the following message:
<P><I>Trying localhost (127.0.0.1) at port 4559...</I>
<BR><I>Connected to localhost.</I>
<BR><I>220 Gruft.Wollis server (HylaFAX (tm) Version 4.0pl1) ready.</I>
<BR><I>--> USER root</I>
<BR><I>550 Cannot set privilegs.</I>
<BR><I>Login failed: 550 Cannot set privilegs.</I>
<P>I'm trying since several days, with no success. Please note, that I
can recieve facsimiles without any problems.
<BR>I'm using SuSE-Linux 5.1 with kernel 2.0.32
<P>Thanks for your help!
<P>Bye
<BR>Burkhard
<BR> </HTML>
</x-html>
To: flexfax@sgi.com
Cc: Constantin Teodorescu <teo@flex.ro>
Subject: Re: flexfax: How to set HylaFax to act as a network printer?
Date: Mon, 01 Jun 1998 13:32:51 -0400
From: Glenn Burkhardt <glenn@aoi.ultranet.com>
Sender: owner-flexfax@celestial.com
> Constantin Teodorescu <teo@flex.ro> :
> I would like to configure HylaFax also as a fax-server for the entire
> network, but using printer spooling mechanism, allowing client to print
> to a shared 'fax' printer when they want to fax it, or normally printing
> to a shared 'laser' network printer, from both Linux and W95
> workstations. For example I am using Applixware on Linux and MS Office
> on W95.
This would be a great idea if someone would do it. For personal systems (as opposed to servers), the right answer to sending a fax is for applications to
print to a fax printer (just as WHFC has been implemented for Win95). The problem in Unix, of course, is how to get the phone number (or other information needed for the cover page).
Forcing the users to put some string into the file to provide the phone number is a kludge, error prone, and a nuisance for the users (they have to remember to do it, they have to remember how to get it just right).
For desktop Unix systems, there's an obvious screen on which to pop up the dialog window. The question is harder for central server configurations like we run here - one system running hylafax, and many X terminals running off of it (or other systems).
Yes, of course we all know how to use tkhylafax or sfax, but the fact of the matter is, to compete in the desktop arena, the many operation approach is a loser. Instead of printing postscript to a file, invoking another program,
telling the program which file to send, the user ought to be able to select 'FAX' as the output device, and just do it.
More integration with applications is even more desireable. There was a request a while ago for picking up phone numbers automatically from the Goldmine contact database. Uli Eckhardt had a technique to do it using OLE. I wouldn't know where to begin to do this with Unix applications. But it's deficiencies like this that make folks turn to Win95 from Unix.
