01-14-2008
I'll check it out. Thanks for the quick response.
10 More Discussions You Might Find Interesting
1. Cybersecurity
does any one know how to kill an idle session?
I want to kill any idle sessions after 30 min... Local or remote....
i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure.....
ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies
2. UNIX for Dummies Questions & Answers
I'm looking for some help, please!
I'm trying to kill any idle user processes over 40 Minutes.
I have tried putting TMOUT=2400
within the users .profile
However this does not seem to be working.
We run aix 4.3.3
with ORACLE 7.3
The above works o.k. when the user is only within the... (3 Replies)
Discussion started by: annette
3 Replies
3. HP-UX
My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Discussion started by: rfmurphy_6
5 Replies
4. AIX
How to set a timer for log out users that have been idle for a long time? It is a AIX 5L (0 Replies)
Discussion started by: wtofu
0 Replies
5. Shell Programming and Scripting
I am trying to write a script that will list the idle users on my system which is running HPUX 11.11. The script is currently written as :
who -u > /home/rfm/scripts/user.txt
echo " There are currently... "
wc -l /home/rfm/scripts/user.txt
echo " User logins on System : `uname -n` ... (3 Replies)
Discussion started by: rfmurphy_6
3 Replies
6. Shell Programming and Scripting
I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies
7. Shell Programming and Scripting
Please help, im modifing an idle script to capture (not kill) users who havee been idle over a time. now i've got to work with the exection of users whos idle time gove over 24 hrs and becomes "old". please advice on how to correct...
#Clear old report, generate new data and new report
echo "\n... (1 Reply)
Discussion started by: pbonilla
1 Replies
8. UNIX for Advanced & Expert Users
Im "supporting" at least 2500 HP-UX workstations with CAD-related software with the B.11.11 build. I cant say anymore than that because of my companys sligtly paranoid security policy .
The last few days a new problem has arised from nowhere.
The problem is that users gets logged off when the... (5 Replies)
Discussion started by: Laoinjo
5 Replies
9. HP-UX
Hi,
In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Discussion started by: efrenba
12 Replies
10. Shell Programming and Scripting
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies
LEARN ABOUT DEBIAN
sasl_checkapop
sasl_checkapop(3) SASL man pages sasl_checkapop(3)
NAME
sasl_checkapop - Check an APOP challenge/response
SYNOPSIS
#include <sasl/sasl.h>
int sasl_checkapop(sasl_conn_t *conn,
const char *challenge,
unsigned challen,
const char *response,
unsigned resplen);
DESCRIPTION
sasl_checkapop() will check an APOP challenge/response. APOP is an optional POP3 (RFC 1939) authentication command which uses a shared
secret (password). The password is stored in the SASL secrets database. For information on the SASL shared secrets database see the System
Administrators Guide in the doc/ directory of the SASL distribution.
If called with a NULL challenge, sasl_checkapop() will check to see if the APOP mechanism is enabled.
RETURN VALUE
sasl_checkapop returns an integer which corresponds to one of the following codes. SASL_OK indicates that the authentication is complete.
All other return codes indicate errors and should either be handled or the authentication session should be quit. See sasl_errors(3) for
meanings of return codes.
CONFORMING TO
RFC 4422, RFC 1939
SEE ALSO
sasl(3), sasl_errors(3)
SASL
29 June 2001 sasl_checkapop(3)