|
From: Jan S. <ha...@st...> - 2010-05-28 08:52:07
|
On May 28 07:08:40, pj...@pj... wrote:
> Jan Stary wrote:
> > > ~> play -q backing.wav &
> > > doesn't run in the background, it enters Stopped state :-(
> >
> > Show us the output of ps(1) that proves this.
>
> ~> play -q backing.wav &
> [1] 1586
> ~> # complete silence :-(
> ~> jobs
> [1]+ Stopped play -q backing.wav
> ~> ps -p 1586
> PID TTY TIME CMD
> 1586 pts/6 00:00:00 play
Are you sure this is actually bash?
What is your $SHELL? (echo $SHELL)
It seems that saying '&' at the end of your command line
of your shell not only puts the process to background,
but also stops it. I don't think bash does that.
Also, it's your shell that says 'stopped'. Can we also get
a ps(1) output that says so to be sure? (Say, 'ps -l'?)
Have you tried starting some other processes like this?
Have you tried starting sox this in other shells?
> > FWIW, `play -q backing.wav &` works as expected here i.e. it does play.
Let's first be sure about what shell you are using.
> Hmm... OK, I'm using up-to-date debian squeeze:
> ~> bash --version
> GNU bash, version 4.1.5(1)-release (i486-pc-linux-gnu)
This doesn't mean you are running bash now.
$ csh
www:hans {23} bash --version
GNU bash, version 3.2.48(1)-release (i386-unknown-openbsd4.5)
Copyright (C) 2007 Free Software Foundation, Inc.
|