Hello.
So first: this thread must not even start if the answer is "bash
justs sends a signal to the job's entire process group, if the
programs do not properly deal with that it cannot help that".
(ogg123 in particular is known to have signal issues.)
This just in case possible changes brought in possible bugs.
I have to workaround an inconvinience and therefore have a shell
wrapper around music playing over bluetooth
$ playbt ...ogg
^ran over an hour, but i needed that terminal, so
^Z
[1]+ Stopped playbt ..
$ bg
[1]+ playbt .. &
^i move the job to the background.. the music starts playing
again, .. but only for a few seconds..
$ jobs
[1]+ Running playbt ... &
$ kill -CONT %1
I have to -CONT kill the job to make all processes of "playbt"
work again:
steffen 3111 3106 0 0.0 2551 6940 Ss+ 00:00:00 Oct21 pts/5 \_
-bash
steffen 24711 3111 0 0.0 662 272 S 00:00:00 Oct21 pts/5 |
\_ /bin/sh /home/steffen/usr-kent-crux-linux-x86_64/bin/playbt ...
steffen 24712 24711 0 0.5 22646 5836 Sl 00:00:25 Oct21 pts/5 |
\_ ogg123 -q -d wav -f - ...
steffen 24713 24711 0 1.1 4533 6420 Sl 00:00:54 Oct21 pts/5 |
\_ sox --no-show-progress --input-buffer 4194304 -t wav - -t alsa bass -20
treble +8
Ie playbt here actually runs ($i being the current file)
p='ogg123 -q -d wav -f -'
$p "$i" | $sox --no-show-progress --input-buffer 4194304 -t wav - -t
alsa bass -20 treble +8
Ie i presume playing then stops once the buffer runs empty, and
only a real -CONT can make the pipeline flow again, which makes me
struggle.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
