02-16-2015
I think that these are sessions that are yet to log in though. You are also assuming that the users drop to the command line, which can be a very dangerous place to let business users get to.
I have a job that scans and terminates idle sessions from the application to handle that.
Your time-out setting is also 360 seconds, because there is a warning issued which has a further 60 seconds delay before the shell exists.
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We use SCO OSR5 with TermLIte to create telnet sessions.
If you accidently click X on the TermLite screen and exit the session you leave process running. I've heard of a program that will allow you to re-connect to these 'floating' sessions and then be able to carry on your session.
Does anyone... (2 Replies)
Discussion started by: mikeh
2 Replies
2. Cybersecurity
On AIX 4.3.3 , how telnet access will be allowed to few users only whereas other will not be able to telnet the server? (6 Replies)
Discussion started by: amit
6 Replies
3. UNIX for Advanced & Expert Users
Anyone know how to limit the telnet sessions on a per user basis on an HP UX Box.
I would like to limit the Maximum number of telnet seesions a user can open at any give time to around 4 or 5. I have been looking and looking and do not seem to be able to find anything on this. Any help would be... (2 Replies)
Discussion started by: Witlr
2 Replies
4. UNIX for Dummies Questions & Answers
I have put TMOUT=1800;export TMOUT in the /etc/profile, put it does not work, by the way the root default shell is sh. but I wana every one including root to terminate the session after setting idle for 1800 seconds. thank for the help. (1 Reply)
Discussion started by: kahn630
1 Replies
5. UNIX for Dummies Questions & Answers
we moved to new server this weekend.
npty nstrpty nstrtel all set to 700
now this AM, users are getting on and after 60 (which was the default for those parms) users - everyone else gets a telnet msg.
I urgently need to know what is causing this and how to fix.
thank you.
Lisa (3 Replies)
Discussion started by: LisaS
3 Replies
6. Solaris
I am trying to find the following information regarding the logging of telnet sessions within a Solaris 10 environment:
(1) How can I tell if the logging of telnet sessions is enabled on a Solaris 10 machine?
(2) Assuming that the logging of telnet sessions is not enabled, what is the... (1 Reply)
Discussion started by: RobSand
1 Replies
7. Forum Support Area for Unregistered Users & Account Problems
Hello,
I have a busybox with tinylogin. How can I log user out when I found the telnet session is idle for 10 seconds?
I set
TMOUT=10
export TMOUT
in /etc/profile
I found it doesn't work for me.
Can anybody help me?
Thanks a lot!
jing (1 Reply)
Discussion started by: jing han
1 Replies
8. HP-UX
Currenly my hp-ux server can take the default of 60 telnet connections,
i want to know how i can increase this. and also can i effect such changes without doing a reboot.
My server is HP-UX B.11.23 (1 Reply)
Discussion started by: tomjones
1 Replies
9. Solaris
hello guys, Does anybody know how I can log all the telnet sessions for a specific IP.
For instance, anybody who make a telnet to IP x.x.x.x this session will be logged. the purpose of it is that I need to know every command that people are running on this node.
Any help ?
Thanks. (1 Reply)
Discussion started by: cerioni
1 Replies
10. HP-UX
What kind of problems can be faced if any session which connects to unix server is open for longer time?
How to find out from how much time that session is idle? :) (1 Reply)
Discussion started by: anandgodse
1 Replies
DCOP(1) DCOP(1)
NAME
dcop - Console DCOP client
SYNOPSIS
dcop [--pipe] [--user user] [--all-users] [--session session] [--all-sessions] [--list-sessions] [--no-user-time] [application [object
[function [arguments]]]]
DESCRIPTION
Console DCOP client
OPTIONS
--pipe Call DCOP for each line read from stdin.
This is roughly equivalent to calling while read line ; do dcop $line ; done but because no new dcop instance has to be started for
each line this is generally much faster, especially for the slower GNU dynamic linkers.
--user user
Connect to the given user's DCOP server. This option will ignore the values of the environment vars $DCOPSERVER and $ICEAUTHORITY,
even if they are set.
If the user has more than one open session, you must also use one of the --list-sessions, --session or --all-sessions command-line
options.
--all-users
Send the same DCOP call to all users with a running DCOP server. Only failed calls to existing DCOP servers will generate an error
message. If no DCOP server is available at all, no error will be generated.
--session session
Send to the given KDE session. This option can only be used in combination with the --user option.
--all-sessions
Send to all sessions found. Only works with the --user and --all-users options.
--list-sessions
List all active KDE sessions for a user or all users.
--no-user-time
Don't update the user activity timestamp in the called application (for use in scripts running in the background).
ENVIRONMENT
DCOPSERVER
ICEAUTHORITY
SEE ALSO
dcopclient(1) dcopref(1) dcopfind(1) kdcop(1)
Inside KDE, you can enter help:/kdcop in Konqueror to see the User Manual for kdcop graphical dcop tool.
March 7, 2003 DCOP(1)