[EMAIL PROTECTED] (Marco d'Itri) wrote: > On Mar 05, Jirka Novosad <[EMAIL PROTECTED]> wrote: > >> I believe the problem is the #!/bin/sh line of /etc/init.d/openbsd-inetd. >> It uses the -e switch and when start-stop-daemon exits with a non-zero >> status, the script exits too. > No shit, Sherlock.
Indeed, it seems to me that failing silently is not correct. But what do you think is the right thing to do instead? Force removal of xinetd with conflicts? Force stopping xinetd in the postinst won't fix it completely, because both will be trying to be started again when the machine is rebooted, won't they? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
