09-02-2015
The phrasing may have been a bit unlucky. If a process sent to background tries to read from the terminal, although still having stdin pointing to the terminal, it assumes a stopped state, so it doesn't interfere with the interactive shell. By sending a process to bg, you intentionally cede interactive control.
You can get back "control" by putting it into foreground with the fg command.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages.
How can i terminate this daemon ? ? ?
Regards,
Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies
2. Shell Programming and Scripting
how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 Replies
3. Programming
Hi all
i have simple c program , when i wish to kill the app
im using kill(0,-9) , but it seams this command don't do any thing and the program.
just ignore it .
what im doing wrong here ?
im using HP-UX ia64
Thanks (9 Replies)
Discussion started by: umen
9 Replies
4. Shell Programming and Scripting
Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies
5. Linux
I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies
6. Shell Programming and Scripting
Hi Unix Gurus i am somewhat new to unix scripting so need your help to
create a script as below.
# This script would find the process consuming memory beyond a certain #limit. if the meemory consumption is more than 100% for a period of 1
# minute for the specific process. the script would... (0 Replies)
Discussion started by: robinforlinux
0 Replies
7. Shell Programming and Scripting
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies
8. Shell Programming and Scripting
hi,
Am a newbie to unix and wasnt able to write script to my requirement.
I need a shell script, which should find a process by name and kill it. For eg: let the process name be "abc". I have different processes running by this name(abc), so should kill them all.
Condition would be: if... (7 Replies)
Discussion started by: fop4658
7 Replies
9. Shell Programming and Scripting
Good afternoon
I need to KILL a process in a single command sentence, for example:
kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'`
That sentence Kills the process ID corresponding to the program CAL255.4ge.
However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
10. Shell Programming and Scripting
hi guys
i had written a shell script Display Information of all the File Systems
i want to find the pid and kill the process after few minutes.how can i obtain the pid and kill it???
sample.sh
df -a >> /tmp/size.log
and my cron to execute every minute every hour every day
* *... (5 Replies)
Discussion started by: azherkn3
5 Replies
pcastctl(8) BSD System Manager's Manual pcastctl(8)
NAME
pcastctl -- Podcast Producer daemons control interface
SYNOPSIS
pcastctl status target on|off|start|stop|restart
OPTIONS
The available options are as follows:
status print status of running daemons
target affect agent or server daemon
start|stop|restart explicitly start/stop/restart daemon. Note that 'restart' will kill all instances of a given daemon, as will
'stop' if none is specified in the pid file.
RETURN VALUES
0 Completed succesfully.
1 Action failed
10 Not run as root.
50 Target not recognized: use 'a', or 's'.
51 Action not recognized: use start|stop|restart
52 Executables not found; may need to reinstall Podcast Producer.
53 Process directory not found; may need to reinstall Mac OS X.
54 Timeout waiting for action to complete.
55 Launchd manipulation failure.
FILES
/usr/libexec/podcastproducer/pcastagentd
Podcast Producer agent daemon
/usr/share/podcastproducer/pcastserverd
Podcast Producer server daemon
/var/run/pcastagentd.pid
Podcast Producer agent process ID
/var/run/pcastserverd.pid
Podcast Producer server process ID
/System/Library/LaunchDaemons/com.apple.pcastagentd.plist
Launchd agent daemon control file
/System/Library/LaunchDaemons/com.apple.pcastserverd.plist
Launchd server daemon control file
EXAMPLES
status of Podcast Producer agent daemon
$ pcastctl agent status
edit launchd configuration to launch server on system startup
$ pcastctl server on
DIAGNOSTICS
Warning: Warning: ## copies of (pcastagentd|pcastserverd) already running
Trying to launch another daemon when one or more already running; will usually succeed, but may cause unpredictable behavior.
See also RETURN VALUES, above.
ERRORS
Error: failed to launch (executable)
Tried to start/restart a give daemon, but failed.
Error: process 'executable' not currently running
Tried to kill a process which did not exist.
SEE ALSO
pcast(1) launchd(8)
HISTORY
This program was first introduced in Mac OS X 10.5 "Leopard". It was inspired by xgridctl(8).
BUGS
pcastctl(8) uses kill -TERM to allow the daemons a chance to die gracefully; there is currently no way to force a kill -KILL.
Bug reports can be sent to bugreport.apple.com
Feedback can be sent to podcastproducer@apple.com
Mac OS September 29, 2004 Mac OS