Search Results

On UNIX and UNIX-like systems, you can think of a foreground job as one that is connected to a keyboard and a background job is one that is not connected to a keyboard at that time. In a given...

Have you considered multiple instances of this script running at once? pgrep allows matching only to processes from the current session with --session 0 this may stop you subshell hanging around...

I guess that all the chromes you see "several times during actual browsing" are child processes created / spawned by the parent chrome. When killing that, all child processes will disappear as well....

Yes, exactly. The command kill sends a signal to a (exactly one) process, identified by the given process ID. Issue a

kill -l

to see a list of signals your system is able to send. killall, on...

It is time to correct a few of my not-so-precise statements above. Suffice it to say i learned something new myself yesterday. Many thanks to RudiC who pointed out my misconception to me.



A...

What RudiC is trying to show you is the following: you have one script:



And in another script you call it and put it in the background:



In fact you need to take out your comments or at...

Not sure the killall will work satisfyingly ... kill $PID will.

Just append the kill command - whichever you use - to the chrome.sh script so it will execute when chrome terminates.

In addition to what my colleague RudiC already said: please always state your OS, its version, your shell, its version and perhaps other relevant properties of your environment depending on your...

Welcome to the forum.


One option would be to create a wrapper script that, when launched / clicked,

- puts above loop into background, keeping its PID
- runs chrome in foreground until...