Active Topics
-
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 2 hrs, 46 mins ago -
Maemo repository (5)
to Community by dredlok706 - 1 day, 21 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 2 days ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 18 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 6 hrs ago - more...
|
2013-08-17
, 14:42
|
|
Posts: 10 |
Thanked: 81 times |
Joined on Nov 2009
@ Espoo
|
#2
|
In a rush, but here are some pointers
$ ps | grep '[v]lc'
That grep won't match the grep itself, so no need for the grep -v to remove it
However, the big gun for finding processes, and killing them, are these two:
$ pgrep vlc
$ pkill vlc
I know these commands are enabled on the old R&D images that I'm still running on my old devices, not sure if it's in the released shell.
$ ps | grep '[v]lc'
That grep won't match the grep itself, so no need for the grep -v to remove it
However, the big gun for finding processes, and killing them, are these two:
$ pgrep vlc
$ pkill vlc
I know these commands are enabled on the old R&D images that I'm still running on my old devices, not sure if it's in the released shell.
|
|
2013-08-17
, 15:54
|
|
Posts: 466 |
Thanked: 661 times |
Joined on Jan 2009
|
#3
|
Why kill -9? You should try plain "kill". If the process is responding normally, it should quit gracefully. Only do a "-9" if you intend a "force quit."
There could be something wrong with the more selective grep. You may want to double check that your 'kill' line is even getting executed.
instead of
try:
to add some logging. If there's nothing in the log, then the grep isn't doing what you want.
Also, be careful with something like "8891*" as this is treated as a regular expression and the "*" is not the same as the "*" in bash, where it's a glob character and not a regular expression meta-character.
There could be something wrong with the more selective grep. You may want to double check that your 'kill' line is even getting executed.
instead of
Code:
kill -9 $i
Code:
echo 'killing '"${i}" >> kill.log && kill "${i}"
Also, be careful with something like "8891*" as this is treated as a regular expression and the "*" is not the same as the "*" in bash, where it's a glob character and not a regular expression meta-character.
I have a routine that I user for killing selected tasks:-
for i in `ps aux|grep "vlc" |grep -v grep | awk '{print $1}' ` ; do kill -9 $i doneIf I modify the code in any way to be more selective in killing my vlc task, sometihing like:-
for i in `ps aux|grep "vlc -I dummy --volume 120 http://name:password@localhost:9981/stream/channelid" |grep -v grep | awk '{print $1}' ` ; do kill -9 $i doneAnyone here able to tell me why?
I have changed the code in any number of ways to select just this type of vlc task, using grep "9981*, grep "stream"..... Only grep "vlc" seems to work.
I thought I knew how this code worked, very myserious!