* Philip Guenther <[email protected]> [081223 19:30]:
Date: Tue, 23 Dec 2008 18:23:23 -0800
From: Philip Guenther <[email protected]>
To: OpenBSD Misc <[email protected]>
Subject: Re: no sound with aucat -l
Content-Type: text/plain; charset=ISO-8859-1
Sender: [email protected]
On Tue, Dec 23, 2008 at 4:44 PM, Steven <[email protected]> wrote:
...
So, when an already running instance of aucat is running I see:
$ sudo aucat -l &
[1] 30719
$
[1] + Stopped (tty output) sudo aucat -l
So it's not "stopped input", sorry about the misleading error
message.
(Also, in case you missed the previous mention of it, you shouldn't
run aucat using sudo.)
No, I got that. Just had some issues running it as non-root.
That's fixed now, so thanks.
I'm a little concerned about pkill reporting that programs have been killed
when they're still running.
pkill is just reporting that it sent the signal successfully. Whether
that will actually kill the process depends on other factors that
pkill can't directly detect. In particular, the only signals that can
be delivered to a stopped process are SIGCONT and SIGKILL. All other
signals are left pending until the process is continued.
I see. Thanks for setting me straight. :-)
--
W. Steven Schneider <[email protected]>
