This happens if you have started the Oracle listener in the current shell,
and the listener does not completely disconnect its streams (as a daemon process should do).
Work around: associate the process' stdin (0) stdout (1) stderr(2) with /dev/null
This User Gave Thanks to MadeInGermany For This Post:
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT CENTOS
systemd-logind.conf
SYSTEMD-LOGIND.CO(5) systemd-logind.conf SYSTEMD-LOGIND.CO(5)NAME
systemd-logind.conf - Login manager configuration file
SYNOPSIS
systemd-logind.conf
DESCRIPTION
This files configures various parameters of the systemd login manager.
OPTIONS
All options are configured in the [Login] section:
NAutoVTs=
Takes a positive integer. How many virtual terminals to allocate by default and when switched to autospawn autovt services on (if they
are otherwise unused). These services are instantiated from a template of autovt@.service with the virtual terminal TTY name, e.g.
autovt@tty4.service. By default autovt@.service is linked to getty@.service, i.e. login prompts are started dynamically as the user
switches to unused virtual terminals, and this parameter hence controls how many gettys are available on the virtual terminals.
Defaults to 6. When set to 0, automatic spawning of autovt services is disabled.
KillUserProcesses=
Takes a boolean argument. Configures whether the processes of a user should be killed when she or he completely logs out (i.e. after
her/his last session ended). Defaults to no.
KillOnlyUsers=, KillExcludeUsers=
These settings take space separated lists of user names that influence the effect of KillUserProcesses=. If not empty only processes of
users listed in KillOnlyUsers will be killed when they log out entirely. Processes of users listed in KillExcludeUsers= are excluded
from being killed. KillExcludeUsers= defaults to root and takes precedence over KillOnlyUsers= which defaults to the empty list.
Controllers=, ResetControllers=
These settings control the default control group hierarchies users logging are added to. When logging in users will get private control
groups in all hierarchies listed in Controllers= and be reset to the root control group in all hierarchies listed in ResetControllers=.
Controllers= defaults to the empty list, ResetControllers= defaults to cpu.
Note that setting KillUserProcesses=1 will break tools like screen(1).
Note that KillUserProcesses=1 is a weaker version of kill-session-processes=1 which may be configured per-service for pam_systemd(8). The
latter kills processes of a session as soon as it ends, the former kills processes as soon as the last session of the user ends.
SEE ALSO systemd(1), systemd-loginctl(1), systemd.conf(5)AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
systemd 10/07/2013 SYSTEMD-LOGIND.CO(5)