I would expect to see nothing in the 3rd command below, but clearly my expectations are incorrect. Why?
$ sudo fuser -v /dev/snd/*
USER PID ACCESS COMMAND
/dev/snd/controlC0: joeuser 2339 F.... pulseaudio
/dev/snd/controlC2: joeuser 2339 F.... pulseaudio
/dev/snd/pcmC0D7p: joeuser 2339 F...m pulseaudio
/dev/snd/pcmC2D0c: joeuser 2339 F...m pulseaudio
/dev/snd/pcmC2D0p: joeuser 2339 F...m pulseaudio
$ kill 2339
$ sudo fuser -v /dev/snd/*
USER PID ACCESS COMMAND
/dev/snd/controlC0: joeuser 2339 F.... pulseaudio
/dev/snd/controlC2: joeuser 2339 F.... pulseaudio
/dev/snd/pcmC0D7p: joeuser 2339 F...m pulseaudio
/dev/snd/pcmC2D0c: joeuser 2339 F...m pulseaudio
/dev/snd/pcmC2D0p: joeuser 2339 F...m pulseaudio
The kill command just sends a signal to the process, and the default signal (when you don't select one), is trapped by the process and maybe ignored or handled in some other way. Use signal -9 , which is the non-maskable signal, to ungracefully kill the process. You might check any documentation of the process to possibly find a signal which will tell the process to clean up and terminate, but -9 is the usual "just kill it" approach.
kill -9 2339
should kill it since you own the process. or from the names for the signals (list from kill -l)
kill SIGKILL 2339
この記事はインターネットから収集されたものであり、転載の際にはソースを示してください。
侵害の場合は、連絡してください[email protected]
コメントを追加