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] faxstat problem on FC2?



Ok.

Here's my experience with PAM.

Installed it with mysql plugin - sig 11 all over the place. Couldn't work it out, recompiling the server, installing uninstalling bits and pieces.

It turns out the mysql pam plugin has a fit if you do anything out of the ordinary - a space in the wrong place, wrong column type etc. This then has a run on effect and pam crashes then the hylafax process.

The moral of the story is - make sure your pam setup is perfect!

This works in FC1

hylafax

auth       required     pam_stack.so service=system-auth debug
account    required     pam_stack.so service=system-auth debug

system-auth

auth        required      /lib/security/$ISA/pam_env.so
auth        sufficient    /lib/security/$ISA/pam_unix.so likeauth nullok
auth        required      /lib/security/$ISA/pam_deny.so

account required /lib/security/$ISA/pam_unix.so

password required /lib/security/$ISA/pam_cracklib.so retry=3 type=
password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5
shadow
password required /lib/security/$ISA/pam_deny.so


session     required      /lib/security/$ISA/pam_limits.so
session     required      /lib/security/$ISA/pam_unix.so



Gerry Doris wrote:
On Fri, 10 Dec 2004, Arnold.Steve wrote:


Howdy:

The hylafax 4.2.0 package on Gentoo provides nothing in /etc except an env file and an init script. Pam is enabled via a USE flag, and I haven't seen any pam issues whatsoever (only tiff issues). There's no hylafax pam config, and pam.d/other has only:

$ cat /etc/pam.d/other
#%PAM-1.0

auth required /lib/security/pam_deny.so

account required /lib/security/pam_deny.so

password required /lib/security/pam_deny.so

session required /lib/security/pam_deny.so

Hylafax access is typically controled by your /var/spool/fax/etc/hosts.hfaxd file.

Also, a sig 11 is very often hardware-related (ie, bad RAM, insufficient cooling, etc), although in this case it doesn't seem like it. Have you tried rebuilding the Hylafax and/or pam rpms? The last Hylafax rpms I built were for RedHat AS 2.1 and cAos (but it was version 4.1.8), however, you should be able to rebuild the 4.2.0 src.rpm on FC2 as well.

HTH, Steve


I have done the following so many times that my typing fingers are numb!!!

- removed all rpm versions of Hylafax
- compiled 4.1.8 and it works fine
- compiled 4.2.0 with/without pam support. Actually, I've done this so many times that I have two separate directories...one with and one without pam support. I just switch between directories and run make install.
- only the version without pam support will work. This is using exactly the same hosts.hfaxd file


With pam support enabled Hylafax receives faxes and sends emails out etc. In other words, it works fine with the exception that I cannot logon to the server to send faxes. Any attempt to logon results in the connection being immediately broken and a signal 11 generated.

Without pam support enabled there are no problems at all. As I said, I'm using the same hosts.hfaxd file for both.

My /etc/pam.d/other file is exactly the same as the one you posted. I've tried changing the lines to produce warning messages in the logs when I login but that doesn't work at all. It seems that pam is not talking to hfaxd at all.

This is on Fedora Core 2.


____________________ 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*




Project hosted by iFAX Solutions