07-23-2001
thanx but...this prameter only works for ROOT and not regular users. i have trired putting this prameter in .profile of the user, in the /etc/default/login, in the /etc/default/telnetd for telnet sessions and none of them have been successful...
Last edited by Holistic; 07-24-2001 at 05:51 PM..
9 More Discussions You Might Find Interesting
1. 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
2. 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
3. Shell Programming and Scripting
I wrote a script to kill users idle more than 1/2 hour, ignoring those in an exception list. Here is the script as it is now:
#! /usr/bin/awk -f
BEGIN {
system("who -u | sort +5 > /tmp/loginfile");
system("echo User Sessions Killed > /tmp/killedlogins");
... (2 Replies)
Discussion started by: PapaBear
2 Replies
4. UNIX for Dummies Questions & Answers
Still it is not working.
I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies
5. Solaris
Hi,
I am accessing a solaris server via client machine.
My problem is that every session is expiring within 1 minute if it kept idle. I am facing problem as i have to enter the credentials around 30 to 40 times per day.
I tried to set the TMOUT variable but it does n't work.
Please help... (7 Replies)
Discussion started by: vamshikrishnab
7 Replies
6. Shell Programming and Scripting
Hello,
I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem.
my script is,
---
while true
do
./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt
echo "Restarting `date`"
done
---
As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies
7. 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
8. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
9. HP-UX
Hi,
I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen?
Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
LEARN ABOUT MINIX
login.krb5
LOGIN(8) System Manager's Manual LOGIN(8)
NAME
login.krb5 - kerberos enhanced login program
SYNOPSIS
login.krb5 [-p] [-fFe username] [-r | -k | -K | -h hostname]
DESCRIPTION
login.krb5 is a modification of the BSD login program which is used for two functions. It is the sub-process used by krlogind and telnetd
to initiate a user session and it is a replacement for the command-line login program which, when invoked with a password, acquires Ker-
beros tickets for the user.
login.krb5 will prompt for a username, or take one on the command line, as login.krb5 username and will then prompt for a password. This
password will be used to acquire Kerberos Version 5 tickets (if possible.) It will also attempt to run aklog to get AFS tokens for the
user. The version 5 tickets will be tested against a local krb5.keytab if it is available, in order to verify the tickets, before letting
the user in. However, if the password matches the entry in /etc/passwd the user will be unconditionally allowed (permitting use of the
machine in case of network failure.)
OPTIONS
-p preserve the current environment
-r hostname
pass hostname to rlogind. Must be the last argument.
-h hostname
pass hostname to telnetd, etc. Must be the last argument.
-f name
Perform pre-authenticated login, e.g., datakit, xterm, etc.; allows preauthenticated login as root.
-F name
Perform pre-authenticated login, e.g., datakit, xterm, etc.; allows preauthenticated login as root.
-e name
Perform pre-authenticated, encrypted login. Must do term negotiation.
CONFIGURATION
login.krb5 is also configured via krb5.conf using the login stanza. A collection of options dealing with initial authentication are pro-
vided:
krb5_get_tickets
Use password to get V5 tickets. Default value true.
krb_run_aklog
Attempt to run aklog. Default value false.
aklog_path
Where to find it [not yet implemented.] Default value $(prefix)/bin/aklog.
accept_passwd
Don't accept plaintext passwords [not yet implemented]. Default value false.
DIAGNOSTICS
All diagnostic messages are returned on the connection or tty associated with stderr.
SEE ALSO
rlogind(8), rlogin(1), telnetd(8)
LOGIN(8)