05-20-2010
Session never expired If i closed client prompt
Hi,
I need a solution. I am using Putty/CRT to login in a AIX server from my windows machine. When i closed my putty/CRT prompt from windows client, server session is expire.
Ex. I have run a script to take RMAN backup from PUTTY/CRT command window, After closing command window RMAN backup failed to complete.
* Solution Other than nohup, VNC screen.
& Suppose i have logged out from server, But my command will running in backgrournd, After log in i want to see my previous command execution screen.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why?
AHHHH!!
I have been connecting to the server with the line: ssh userid@website.com
The remote server accepts my password; logs me in with ssh; posts a lovely welcome message AND closes the session. Is this a "term... (0 Replies)
Discussion started by: xprankard
0 Replies
2. Solaris
Hi
I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed.
What I did:
I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies
3. Solaris
I'm on a Solaris 8 box that is not prompting users to change their password after it has expired. I have an older Solaris 8 box that does. We're accessing both via ssh. We have recently built the box that doesn't prompt from scratch. Obviously, we've overlooked something but we don't know what.... (2 Replies)
Discussion started by: mark24p
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I ran a shell script in the foreground but it seems that the shell script teminated when the session expired. Please let me knw if it's possible or hypothesis is incorrect ASAP. (2 Replies)
Discussion started by: Ankgne
2 Replies
5. Solaris
Hi,
I am using DSEE 6.3 to authenticate and authorize my Solaris 9 and 10 users. Everything works fine except password expiration. I use built-in global password policy for all users. The policy works well. However I could not find the right pam configuration in order to prompt users at ssh... (2 Replies)
Discussion started by: niyazi
2 Replies
6. Shell Programming and Scripting
I have a master host I want to use to issue some start/stop of LDAP services.
I changed the client hosts /etc/sudoers to have
Defaults:infra !requiretty
The master host kicks off the jobs using the infra account doing a ssh session to the infra account on the clients.
#!/bin/ksh
ps -fu... (5 Replies)
Discussion started by: J-Man
5 Replies
7. Solaris
Hi,
I would appreciate some help.
I remotely access, across a VPN, an M5000 and when I connect to the XSCF I can then access the OS using console -d0 and then I can get to the console.
The problem I have is that I need to run something which will take many hours and I can't run it in the... (6 Replies)
Discussion started by: giles.cardew
6 Replies
8. AIX
Hi everyone,
This is a strange thing, sometimes when I type > exit from root session, i get a message
> There are processes running
after this message is displayed the oracle listener dies out and have to startup the listener again.
but this doesn't have always.
Where should I start to... (5 Replies)
Discussion started by: filosophizer
5 Replies
9. AIX
Is there a way that I can remotely control a user's ssh session so I can see what they are doing and walk them through the problem they are having on my AIX based application? (2 Replies)
Discussion started by: De@nneG
2 Replies
10. Red Hat
Hi,
I am getting the -bash-3.2# prompt whenever I am trying to logging in the RHEL machine
# ssh mindnic-02
root@mindnic-02's password:
Last login: Thu May 25 14:06:31 2017 from 10.250.107.81
Could not chdir to home directory /root: No such file or directory
-bash-3.2#
Please help... (7 Replies)
Discussion started by: muzaffar.k
7 Replies
LEARN ABOUT XFREE86
xkill
XKILL(1) General Commands Manual XKILL(1)
NAME
xkill - kill a client by its X resource
SYNOPSIS
xkill [-display displayname] [-id resource] [-button number] [-frame] [-all]
DESCRIPTION
Xkill is a utility for forcing the X server to close connections to clients. This program is very dangerous, but is useful for aborting
programs that have displayed undesired windows on a user's screen. If no resource identifier is given with -id, xkill will display a spe-
cial cursor as a prompt for the user to select a window to be killed. If a pointer button is pressed over a non-root window, the server
will close its connection to the client that created the window.
OPTIONS
-display displayname
This option specifies the name of the X server to contact.
-id resource
This option specifies the X identifier for the resource whose creator is to be aborted. If no resource is specified, xkill will
display a special cursor with which you should select a window to be kill.
-button number
This option specifies the number of pointer button that should be used in selecting a window to kill. If the word "any" is speci-
fied, any button on the pointer may be used. By default, the first button in the pointer map (which is usually the leftmost but-
ton) is used.
-all This option indicates that all clients with top-level windows on the screen should be killed. Xkill will ask you to select the
root window with each of the currently defined buttons to give you several chances to abort. Use of this option is highly discour-
aged.
-frame This option indicates that xkill should ignore the standard conventions for finding top-level client windows (which are typically
nested inside a window manager window), and simply believe that you want to kill direct children of the root.
CAVEATS
This command does not provide any warranty that the application whose connection to the X server is closed will abort nicely, or even abort
at all. All this command does is to close the connection to the X server. Many existing applications do indeed abort when their connection
to the X server is closed, but some can choose to continue.
XDEFAULTS
Button Specifies a specific pointer button number or the word "any" to use when selecting windows.
SEE ALSO
X(7), xwininfo(1), XKillClient and XGetPointerMapping in the Xlib Programmers Manual, KillClient in the X Protocol Specification
AUTHOR
Jim Fulton, MIT X Consortium
Dana Chee, Bellcore
XFree86 Version 4.7.0 XKILL(1)