From: Pete S. <pst...@ve...> - 2008-04-05 04:00:14
|
PS = Pete Stieber PS>>> Thanks Kevin. I'm trying to understand the Jazz++ PS>>> zombie process that lives on when I exit Jazz++. PS>>> It looks like it has to do with the ALSA connection. PS>>> When I reboot, the ALSA close message even fails. PS>>> This doesn't happen on the Fedora 8 box I test on. KC = Kevin Cosgrove KC>> Rather than rebooting, is there an alsa service in KC>> /etc/init.d/... which could be restarted with the KC>> 'service' command? PS> Thanks for suggesting this Kevin. I'm a long time PS> Red Hat/Fedora user and though the "service" PS> command was specific to Red Hat. PS> PS> I'm starting to think there is a problem that is PS> independent of Jazz++. I tried restarting PS> ALSA from a cold boot and it also has problems... PS> PS> # service alsa restart PS> Doing alsactrl to store mixer settings... [ OK ] PS> Shutting down ALSA sound driver (version 1.0.14): no. (sound is being PS> used by pid 6272)) [FAILED] PS> ALSA driver (version 1.0.14) is already running. PS> PS> Process 6272 is the sound mixer applet PS> (/usr/lib/mixer_applet2). PS> PS> Is this normal. I thought root should be able to PS> restart this service. PS> PS> When I check to see what ALSA version I PS> have installed... PS> $ rpm -qa | grep alsa PS> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-oss0-1.0.14-2mdv2008.0 PS> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS> alsa-plugins-1.0.14-7mdv2008.0 PS> PS> Should 1.0.14 be mixed with 1.0.15? PS> PS> I don't want to get too caught up in Mandriva PS> specific problems. Maybe I botched the install? PS> PS> Any ideas Kevin? I can't even stop the process with # service alsa force-stop This command tries to stop all processes attached to alsa, but gets stuck trying to kill the Jazz++ process with a SIGKILL. I'm not sure what to do next. Pete |