Sponsored Content
Operating Systems AIX Oracle Listener gets killed when root session is closed Post 302884418 by radoulov on Monday 20th of January 2014 09:42:46 AM
Old 01-20-2014
If configured correctly, the listener should come and remain up with lsnrctl start <listener_name>.
Inspect the listener log file for errors (use lsnrctl status <listener_name> to get the log location and filename).
 

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?

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. UNIX and Linux Applications

Oracle - How to manage listener log files

Dear expert, I'm newbie in oracle, I have a problem regarding the listener log files under alert directory and trace directory(please refer to below). As the oracle hard disk size only 10GB, I have to manually delete the log files under alert directory and trace directory. Is that anyway for... (1 Reply)
Discussion started by: yhcheong
1 Replies

3. AIX

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... (2 Replies)
Discussion started by: dearsumon
2 Replies

4. Infrastructure Monitoring

Test if Oracle listener is running

Hi All , I am new to shall scripting, i want write an script for oracle tns and listener. If tns working i want o/p as "Listener and TNS are working" else o/p should be ""Listener and TNS are not Working" below is the command in unix to check the tns status, if no output it means TNS... (3 Replies)
Discussion started by: abdul bari
3 Replies

5. Red Hat

Oracle Listener Error on Red hat 5

Hello everybody, the reason why im posting this thread is because i've installed an oracle test database on RHEL 5, on a localhost (Since it is for test)... the thing is, after i have installed the DB it works just fine, but after i re start it, i get the following errors when i want to go into the... (5 Replies)
Discussion started by: blacksteel1988
5 Replies

6. AIX

SIGHUP killing Oracle Listener Process

I have a cold backup script which backs up my database and then restarts the oracle listener and database at around 01:30 I can see at this time that my database and listener are indeed running. However at around 02:17 my listener process receives a SIGHUP 1 signal from the AIX OS ( version 5.3 )... (2 Replies)
Discussion started by: jimthompson
2 Replies

7. Emergency UNIX and Linux Support

Nohup process getting killed after closing PUTTY session

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

8. Solaris

M5000 XSCF Console disconnecting when putty session is closed

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

9. Solaris

vnc windows unexceptly is closed after given root and passwd

hi all I'm new to solaris my vncviewer windows is closed suddenly after give root and root passwd in solaris 10 sparc machine ... i checked vnc services are online and everything is ok .. but i dont know how to solve this solution... any one face this solution before and share your knowledge ... (1 Reply)
Discussion started by: coolboys
1 Replies

10. What is on Your Mind?

Has Oracle killed HP-UX

Has Oracle killed HP-UX with their gambit of telling the public they would no longer support Itanium? The company I work for in the Dallas, TX area has had several openings for HP-UX administrators and we're having such a tough time finding qualified people to fill them. I have been searching job... (3 Replies)
Discussion started by: keelba
3 Replies
VLOCK-MAIN(8)						     Linux Programmer's Manual						     VLOCK-MAIN(8)

NAME
vlock-main - lock current virtual console SYNOPSIS
vlock-main [plugins...] DESCRIPTION
vlock-main is part of vlock(1), the Virtual Console locking program for Linux. It locks the current session and will only exit if the cur- rent user can authenticate themselves. The root user will also be able to unlock the session, unless disabled at compile time. The com- mand line arguments specify plugins that should be loaded by vlock-main. See vlock-plugins(5) for more information. If plugin support is disabled at compile time, the only supported argument is "all". ENVIRONMENT VARIABLES
The following environment variables can be used to change the behavior of vlock-main: USER If this variable is when vlock-main is run as root (uid 0) vlock locks the screen as this user instead of root. The root password will still be able to unlock the session, unless disabled at compile time. VLOCK_ALL_MESSAGE If this variable is set and all consoles are locked its contents will be used as the locking message instead of the default message. VLOCK_CURRENT_MESSAGE If this variable is set and only the current consoles is locked its contents will be used as the locking message instead of the default message. VLOCK_MESSAGE If this variable is set its contents will be used as the locking message instead of the default. This overrides the former two variables. VLOCK_TIMEOUT Set this variable to specify the timeout (in seconds) after which the screen saver plugins (if any) will be invoked. If this vari- able is unset or set to an invalid value or 0 no timeout is used. See vlock-plugins(5) for more information about plugins. VLOCK_PROMPT_TIMEOUT Set this variable to specify the amount of time (in seconds) you will have to enter your password at the password prompt. If this variable is unset or set to an invalid value or 0 no timeout is used. Warning: If this value is too low, you may not be able to unlock your session. SIGNALS
Several signals are ignored. vlock-main will try to exit cleanly if SIGTERM is received. SEE ALSO
vlock(1), vlock-plugins(5) AUTHORS
Frank Benkstein <frank-vlock@benkstein.net> Linux 28 July 2007 VLOCK-MAIN(8)
All times are GMT -4. The time now is 07:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy