Bug#451704: [Pkg-alsa-devel] Bug#451704: Bug#451704: Latest version takes a lot to shut down

2007-11-29 Thread Ludovic Rousseau

David a écrit :
On my laptop, the next process that stops after alsa is the bluetooth 
and, still, it takes much time.


Are you sure about the reassignation?


Yes.

It really is a bug in pcsc-lite. Sorry.

A simple patch is:
--- pcscd.init  2007-11-29 23:35:28.0 +0100
+++ /etc/init.d/pcscd   2007-11-29 23:51:28.0 +0100
@@ -24,8 +24,7 @@
 NAME=pcscd
 DAEMON=/usr/sbin/$NAME

-PIDFILE=/var/run/pcscd/$NAME.pid
-PUBFILE=/var/run/pcscd/$NAME.pub
+PIDFILE=/var/run/$NAME.pid
 SCRIPTNAME=/etc/init.d/$NAME

 # Gracefully exit if the package has been removed (but not purged).



I will upload a new package soon.

bye


--
 Dr. Ludovic Rousseau




Bug#451704: [Pkg-alsa-devel] Bug#451704: Bug#451704: Latest version takes a lot to shut down

2007-11-28 Thread Elimar Riesebieter
reassign 451704 pcscd

thanks


On Sun, 18 Nov 2007 the mental interface of
David told:

  On Sat, 17 Nov 2007 the mental interface of
  David told:
 
 
 You are a bit geek, aren't you? :-D :-D
 
 
  Could you please test the following:
 
  # /etc/init.d/alsa-utils stop
 
  Another 15 sec?
 
 
 
 No, it is almost instantly. The same when shutting down or rebooting: it
 reads
 
 Setting up ALSA...done.
 
 And, after prompting the done, it stays around 15 seconds. *But, it is
 alsa, and not the next process, to blame*. I know it because in one
 computer, the next process to stop is the bluetooth. The other computer does
 not have any bluetooth, so the next process to stop after alsa is a
 different one (I do not remember which one).

The situation here:

Box #1 rc(0|6).d:
...
lrwxrwxrwx 1 root root  20 Sep 22 14:57 K50alsa-utils -../init.d/alsa-utils*
lrwxrwxrwx 1 root root  15 Nov 14 13:40 K50pcscd - ../init.d/pcscd*
...

# /etc/init.d/pcscd stop
takes 15 sec to finish.
15 sec staying around after alsa-util stop while reboot/shutdown.

# mv K50pcscd _K50pcscd
A very fluent shutdown/reboot

##

Box #2 rc(0|6).d:
...
lrwxrwxrwx 1 root root  20 Sep 22 14:57 K50alsa-utils -../init.d/alsa-utils*
lrwxrwxrwx 1 root root  15 Nov 14 13:40 K74bluetooth -
../init.d/bluetooth*
...
A very fluent shutdown/reboot

Bug reassigned to pcscd.

Elimar

-- 
  what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--



___
Pkg-alsa-devel mailing list
[EMAIL PROTECTED]
http://lists.alioth.debian.org/mailman/listinfo/pkg-alsa-devel




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#451704: [Pkg-alsa-devel] Bug#451704: Bug#451704: Latest version takes a lot to shut down

2007-11-28 Thread David
On my laptop, the next process that stops after alsa is the bluetooth and,
still, it takes much time.

Are you sure about the reassignation?

Thank you


Bug#451704: [Pkg-alsa-devel] Bug#451704: Bug#451704: Latest version takes a lot to shut down

2007-11-28 Thread Elimar Riesebieter
On Wed, 28 Nov 2007 the mental interface of
David told:

 On my laptop, the next process that stops after alsa is the bluetooth and,
 still, it takes much time.

Please post the output of:

$ ls -al /etc/rc(0|6).d | grep -A 3 alsa-ut

 Are you sure about the reassignation?

Yes!

On my powerbook:

lrwxrwxrwx   1 root root   20 Sep 16 18:14 K50alsa-utils - ../init.d/alsa-utils
lrwxrwxrwx   1 root root   19 Aug 29 22:53 K74bluetooth - ../init.d/bluetooth
lrwxrwxrwx   1 root root   16 May 13  2006 K75hdparm - ../init.d/hdparm
lrwxrwxrwx   1 root root   15 May 13  2006 K89klogd - ../init.d/klogd
--
lrwxrwxrwx   1 root root   20 Sep 16 18:14 K50alsa-utils - ../init.d/alsa-utils
lrwxrwxrwx   1 root root   19 Aug 29 22:53 K74bluetooth - ../init.d/bluetooth
lrwxrwxrwx   1 root root   16 May 13  2006 K75hdparm - ../init.d/hdparm
lrwxrwxrwx   1 root root   15 May 13  2006 K89klogd - ../init.d/klogd

and a fluent reboot/shutdown ;)

Elimar

-- 
  Learned men are the cisterns of knowledge, 
  not the fountainheads ;-)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]