06-08-2012
The message doesn't mean PAM forced it to close. It just means that PAM noticed it closing. You get that for any logout.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
I currently run a very long script (two hour left...) on a remote computer through a ssh session. I wonder whats happend if I close the ssh session, or even, the terminal. Is the script running on remote will stop?
Thanks for your answers,
Tp (1 Reply)
Discussion started by: tipi
1 Replies
2. Solaris
Hi
we have a script which establish connection to two other UNIX server through ssh for transfering files
There was no exit command after each ssh connection
the script ends with done
whether this will close all the ssh connection established throgh script which running under cron... (4 Replies)
Discussion started by: GIC1986
4 Replies
3. Shell Programming and Scripting
I am using a shell script to telnet into a remote unix server and execute certain commands. But if any command being executed remotely, throws an error, the script just hangs. And the telnet session does not get closed.
I want to be able to close the session and complete the script execution in... (1 Reply)
Discussion started by: farahzaiba
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have ssh'd into a UNIX server at work from my linux desktop and executed a tar command to backup up some directories to a tape drive. I was wondering would the tar command still execute to completion if I closed my terminal console on my desktop that is connected to the server, would the... (1 Reply)
Discussion started by: mojoman
1 Replies
5. OS X (Apple)
Might anyone have an idea on how to mount an xserve share via ssh, then close the share connection? (3 Replies)
Discussion started by: unimachead
3 Replies
6. Shell Programming and Scripting
I am using Net::SSH::Expect to connect to the device(iLO) with SSH. After the $ssh->login() I'm able to view the prompt, but not able to send any coommands.
With the putty I can connect to the device and execute the commands without any issues.
Here is the sample script
my $ssh =... (0 Replies)
Discussion started by: hansini
0 Replies
7. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
8. Solaris
This is a zone running Solaris 10u8 on a 6320 blade. The global zone is also running 10u8.
One my users is attempting to change his password and getting a following screen:
$ ssh remotesys
Password:
Warning: Your password has expired, please change it now.
New Password:
Re-enter new... (1 Reply)
Discussion started by: bluescreen
1 Replies
9. Emergency UNIX and Linux Support
look at this, as root user change passwd and su -:
I cannot ssh in or rlogin either, (3 Replies)
Discussion started by: bigearsbilly
3 Replies
10. Emergency UNIX and Linux Support
I am running a process in nohup .
nohup getkeys.ksh 132 > 132.out &
When I close the putty terminal,The process is getting killed .
default_signal_handler called for signal no: 1
Is there a way to keep the process running even If I close the terminal (2 Replies)
Discussion started by: prasperl
2 Replies
LEARN ABOUT PLAN9
pam_end
PAM_END(3) Linux-PAM Manual PAM_END(3)
NAME
pam_end - termination of PAM transaction
SYNOPSIS
#include <security/pam_appl.h>
int pam_end(pam_handle_t *pamh, int pam_status);
DESCRIPTION
The pam_end function terminates the PAM transaction and is the last function an application should call in the PAM context. Upon return the
handle pamh is no longer valid and all memory associated with it will be invalid.
The pam_status argument should be set to the value returned to the application by the last PAM library call.
The value taken by pam_status is used as an argument to the module specific callback function, cleanup() (See pam_set_data(3) and
pam_get_data(3)). In this way the module can be given notification of the pass/fail nature of the tear-down process, and perform any last
minute tasks that are appropriate to the module before it is unlinked. This argument can be logically OR'd with PAM_DATA_SILENT to indicate
to indicate that the module should not treat the call too seriously. It is generally used to indicate that the current closing of the
library is in a fork(2)ed process, and that the parent will take care of cleaning up things that exist outside of the current process space
(files etc.).
This function free's all memory for items associated with the pam_set_item(3) and pam_get_item(3) functions. Pointers associated with such
objects are not valid anymore after pam_end was called.
RETURN VALUES
PAM_SUCCESS
Transaction was successful terminated.
PAM_SYSTEM_ERR
System error, for example a NULL pointer was submitted as PAM handle or the function was called by a module.
SEE ALSO
pam_get_data(3), pam_set_data(3), pam_start(3), pam_strerror(3)
Linux-PAM Manual 06/04/2011 PAM_END(3)