09-08-2014
I completely agree with Coron688; everything should be killed.
First question is, How are you logging out? Are you using a terminal emulator? Is the interactive session also still running?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I try to run a script as background job.
script:
#!/usr/bin/csh
/usr/bin/date +20%y-%m-%d > ~/datsql.txt
If I start it I got this output:
tac> ./datermitteln&
293
+ Stopped (SIGTTOU) ./datermitteln&
I insert the following line inside my script, but without any... (3 Replies)
Discussion started by: joerg
3 Replies
2. UNIX for Dummies Questions & Answers
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
Discussion started by: rdbooth
1 Replies
3. UNIX for Dummies Questions & Answers
on gnome i open a terminal and run wget http://soommmething & in the background. because wget shows me downloading progress percentage and download speed continuously, I exit the gnome-terminal
after a while i want to see the download percentage but dont know how. my ps -u myname shows that... (3 Replies)
Discussion started by: babayeve
3 Replies
4. Shell Programming and Scripting
hi, i am just wondering that wen we give the following code we make a process run in background...can the viceversa be performed?i.e can this be made foreground again
# sleep 75&
21751
# (4 Replies)
Discussion started by: sandilya
4 Replies
5. Shell Programming and Scripting
Hi all,
I am currently facing a problem when i am submitting a script to run in the background to collect statistics round the clock on an AIX box. I don't have root authority nor can I set it in cron.
So when i submit the job, it runs fine, but won't let me signoff. It prompts me that... (2 Replies)
Discussion started by: tansha
2 Replies
6. Linux
Hi,
I was running a job in background and because of some immediate work to be done on my machine, I stopped the background job. The real problem comes when I try to restart the same job in the background. To stop I used
stop PID
and to resume the same I use
bg PID
when I do this the... (2 Replies)
Discussion started by: baloo_mia
2 Replies
7. UNIX for Advanced & Expert Users
Hello - I submitted one background job last night and it completed today morning.I want to know exact time the job completed.
I submitted backgroung job like this
nohup cp -Rp /opt/apps/prod/proddb/proddata . &
I want to know when above job completed on UNIX server.Above command... (9 Replies)
Discussion started by: Mansoor8810
9 Replies
8. Shell Programming and Scripting
Hello Everyody,
Having a doubt.
sort file1 &
when we sent a job to the background it returns
Job Number
PID
again if we want to ... (1 Reply)
Discussion started by: knroy10
1 Replies
9. Shell Programming and Scripting
How to bring a backgroud job say sample_script.sh to foreground (4 Replies)
Discussion started by: rafa_fed2
4 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)