by Dou » Thu, 18 Jul 2002 17:38:47
When I type 'killall -STOP mpg321' nothing happens. When I type
'killall -CONT mpg321' it says:
And I can't get it to play again.
Any ideas why this is happening? Do I need to fork something?
Thanks,
Doug
by Dou » Fri, 19 Jul 2002 04:38:52
In addition, if I do kill -STOP <PID>, the process stops and I can doQuote:> Any ideas why this is happening? Do I need to fork something?
More information:
killall -v -STOP mpg321
Killed mpg321(5507) with signal 17
So it is killing it, but the process still continues. -CONT does stop
it. Does anyone know why it works if I use 'kill', but not 'killall'?
Is this a problem with Red Hat 7.3?
-Doug
by Nils O. Sel?sda » Fri, 19 Jul 2002 08:38:04
Probably, there are some recent updated rpms that hopefully correct this,Quote:>> Any ideas why this is happening? Do I need to fork something?
> In addition, if I do kill -STOP <PID>, the process stops and I can do
> kill -CONT <PID> to start it again.
> More information:
> killall -v -STOP mpg321
> Killed mpg321(5507) with signal 17
> So it is killing it, but the process still continues. -CONT does stop
> it. Does anyone know why it works if I use 'kill', but not 'killall'?
> Is this a problem with Red Hat 7.3?
--
System Developer, UtelSystems a/s
w w w . u t e l s y s t e m s . c o m
by Doug » Fri, 19 Jul 2002 15:54:09
> >> Any ideas why this is happening? Do I need to fork something?
> > In addition, if I do kill -STOP <PID>, the process stops and I can do
> > kill -CONT <PID> to start it again.
> > More information:
> > killall -v -STOP mpg321
> > Killed mpg321(5507) with signal 17
> > So it is killing it, but the process still continues. -CONT does stop
> > it. Does anyone know why it works if I use 'kill', but not 'killall'?
> > Is this a problem with Red Hat 7.3?
> Probably, there are some recent updated rpms that hopefully correct this,
> so check out the redhat updates...(www.redhat.com/download , and click the
> bugfixes/security updates link to the right)
> --
> System Developer, UtelSystems a/s
> w w w . u t e l s y s t e m s . c o m
1. killall -STOP xclock... hangs filesystem
HiHo,
I am using kernel 2.0.33 on a P55C (P166MMX) with something that was a
RedHat 3.0.3 some time ago.
In preperation for playing an animation under X I "killall -STOP"ed the two
xclocks and one xosview running on the machine (this I did as
root)(paranoia mode -- I want smooth playback).
I had no problem with the animation, but then, completely independent, I
tried to copy some file around (as normal user) but got a "file too large"
error. The copy operation left the destination file empty (source was like
3kb and there were still enough bytes free left). I then tried to do a
"echo hallo > ttt", to no avail. A file ttt was created, but left empty
again. The same happened on other partitions...
After completely killing the stopped tasks everything worked as normal
again. I have yet to reprocduce this bug. It is not the first time that I
kill -STOP processes for some reason, but the first time such a strange
behaviour has occured -- at least I can't explain it.
Regards, Colin
--
----
Lehr- und Forschungsgebiet Mathemathische Grundlagen der Informatik
University of Technology Aachen Ahornstr. 55, D-52074 Aachen
----
2. Downloading Linux, any order?????
3. kill/killall
5. killall
6. Bootable 4.1.3 and 5.3 on same machine?
8. How to limit # connections to a port
9. Don't like 'killall pppd' in my .bash_profile, but ...
10. Kill a process with a partial name (killall *dip* ???)
11. "killall" for non-Linux machines?
13. killall on AIX