Martin-Éric Racine wrote:
> It's reported by insserv and caused by mismatched boot and shutdown
> orders in the LSB headers of the init script shipped with libchipcard;
> it causes recursive boot/shutdown conflicts between other packages.
Yes, but what exactly is the loop in this case? From the initial report
I can see that rsyslog, udev, sendsigs, nullmailer anc chipcardd seem to
be involved, but not how exactly.
Do you have any pointers to documentation/specs explaining the issue in
more detail?
> Fixing this requires changing the boot dependency order in
> libchipcard's ini script's LSB headers.
Yes, I understood this alread. But *how* exactly should I change the
boot dependency?
Regards
Micha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Martin-Éric,
Martin-Éric Racine wrote:
> It's reported by insserv and caused by mismatched boot and shutdown
> orders in the LSB headers of the init script shipped with libchipcard;
> it causes recursive boot/shutdown conflicts between other packages.
Yes, but what exactly is the loop in this case? From the initial report
I can see that rsyslog, udev, sendsigs, nullmailer anc chipcardd seem to
be involved, but not how exactly.
Do you have any pointers to documentation/specs explaining the issue in
more detail?
> Fixing this requires changing the boot dependency order in
> libchipcard's ini script's LSB headers.
Yes, I understood this alread. But *how* exactly should I change the
boot dependency?
Regards enigmail. mozdev. org/
Micha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkt TOUUACgkQWN0/ 4pnhQbQXQwCfRH9 2CphtX9LbS2tMou eD6C6m x12DLe9vCfN1Yt0 Bo5W0
AEEAniii7v0/
=F0XY
-----END PGP SIGNATURE-----