All'incirca Thu, 20 Dec 2007 16:27:09 +0100, Romain Beauxis <[EMAIL PROTECTED]> sembrerebbe aver scritto:
> Le Thursday 20 December 2007 16:17:03 Giovanni Mascellani, vous avez > écrit : > > This can be avoided, for example, by passing the --oknodo to > > start-stop-daemon, or by managing correctly its failures. > > Sorry I wasn't clear. > > This I understand, but it's the desired behaviour: the package should > not be removed if the daemon didn't exit well, in particular if it's > still running... Well, --oknodo doesn't mask the failure, it only masks the "nothing-to-do" case. If the daemon didn't exit well, start-stop-daemon would anyhow exit with an error status code. > So my question was about the reason why _your_ daemon failed to stop.. > If this is caused by some wrong configuration/anything from your > side, then it's not a bug from the package I guess... My daemon was simply stopped, just because I didn't use peercast-servent. And I think that this shouldn't prevent peercast to be removed. :-) Regards, Giovanni. -- Giovanni Mascellani <[EMAIL PROTECTED]> Pisa, Italy Web: http://giomasce.altervista.org SIP: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] / [EMAIL PROTECTED] GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD 003F FCB0 BB5C 5F1F BF70)
signature.asc
Description: PGP signature
