Re: [hylafax-users] Caught signal 11

[Gerry Doris <gdoris@xxxxxxxxxx>]

On Tue, 30 Nov 2004, Patrice Fournier wrote:

> Quoting Gerry Doris <gdoris@xxxxxxxxxx>:
> 
> > Now when I telnet into the server (from the server) and try and login
> > using the user command I get
> >
> > 230 USER gerry logged in
> >
> > immediately followed by
> >
> > Connection closed by foreign host
> >
> > What I have also found is that in my log files I'm seeing is
> >
> > HylaFAX: CAUGHT SIGNAL 11
> 
> This may have something to do with PAM support. There is a patch on
> bugzilla that may fix this ( See bug 581:
> http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=581 ). It is already in
> current CVS.
> 
> If this doesn't fix the problem, you could try disabling PAM support at
> compilation time and try again. If this solves the problem (and patch on
> bug 581 didn't), we'd need more information about your system setup so we
> can try to reproduce this: what's the content of /etc/nsswitch.conf,
> /etc/pam.d/hylafax (if it exists) and /etc/pam.d/other. Also, a trace of
> hfaxd during a connection would also help.
> 
> If you can't recompile and /etc/nsswitch.conf contains a "group" line with
> a value other than "compat", change it to "compat", do one more test and
> report back the result (with the original value) (revert the change to
> /etc/nsswitch.conf if you don't understand what it does as it may affect
> other programs...)
> 
> --
> Patrice Fournier

Patrice, I think I may have this fixed.  I was checking /etc/pam.d/other 
against some of the other files in the pam.d directory.  I didn't like the 

/lib/security/$ISA/pam_deny.so 

that I had for all 4 entries.  I changed this to 

pam_stack.so service=system-auth

which is consistent with the other files that work.  After re-compiling 
4.2.0 everything appears to be working.  I copied the modified 
/etc/pam.d/other file to /etc/pam.d/hylafax and changed the modified 
/etc/pam.d/other file back to its original values.  Hylafax is still 
working correctly.

I know nothing about pam nor how hylafax actually uses pam.  Is what I've 
down correct?  Is there a better way to handle this?

-- 
Gerry

"The lyfe so short, the craft so long to learne"  Chaucer

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