Re: PAM error messages
"David W. Chapman Jr." <[EMAIL PROTECTED]> writes: > I'm seeing this a lot on a recent 4.5-STABLE to -current upgrade, is > this a problem or something I did wrong? > > dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() > dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() Neither. The PAM policy for login(1) includes pam_unix in the session management chain, but pam_unix does not provide session management services, so you get a warning. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
>> Yesterday I tried to use SWAT for the first time since the PAM configs were >> moved from /etc/pam.conf and I'm getting the following error: >> >> Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open >> /etc/pam.conf >> >> What do I need to do to fix this? > >Recompile the app. I'm guessing it is linked statically, so is not >picking up the latest libpam. I am still getting this error on both -CURRENT machines I use and these machines *are* fully re-built from source with all applications re-built from an up-to-date ports tree. To reproduce: 1) update your world, kernel and /etc to post new pam 2) rm /etc/pam.conf 3) reboot 4) build ports/security/sudo 5) configure sudo if you haven't already (/usr/local/sbin/visudo as root) 6) type "sudo ls" as your authourised sudo user 7) notice the following on your console: Feb 14 12:05:47 blah sudo: PAM _pam_init_handlers: could not open /etc/pam.conf -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Edinburgh PO Box 1500 EDINBURGH South Australia 5111 IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
> Yesterday I tried to use SWAT for the first time since the PAM configs were > moved from /etc/pam.conf and I'm getting the following error: > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > /etc/pam.conf > > What do I need to do to fix this? Recompile the app. I'm guessing it is linked statically, so is not picking up the latest libpam. M -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
On Mon, Feb 11, 2002 at 12:04:53PM +, [EMAIL PROTECTED] wrote: > > Yesterday I tried to use SWAT for the first time since the PAM configs were > > moved from /etc/pam.conf and I'm getting the following error: > > > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > > /etc/pam.conf > > > > What do I need to do to fix this? > > Recompile the app. I'm guessing it is linked statically, so is not > picking up the latest libpam. > Though that sounds logical to me too, I've had the same errors pop up using a self-compiled 'cups'. I haven't had time to try to chase what's going on. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
On Mon, Feb 11, 2002 at 12:04:53PM +, [EMAIL PROTECTED] wrote: > > Yesterday I tried to use SWAT for the first time since the PAM configs were > > moved from /etc/pam.conf and I'm getting the following error: > > > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > > /etc/pam.conf > > > > What do I need to do to fix this? > > Recompile the app. I'm guessing it is linked statically, so is not > picking up the latest libpam. > Though that sounds logical to me too, I've had the same errors pop up using a self-compiled 'cups'. I haven't had time to try to chase what's going on. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
> Yesterday I tried to use SWAT for the first time since the PAM configs were > moved from /etc/pam.conf and I'm getting the following error: > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > /etc/pam.conf > > What do I need to do to fix this? Recompile the app. I'm guessing it is linked statically, so is not picking up the latest libpam. M -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message