Hi, On Thu, Apr 10, 2014 at 03:10:54PM +0200, Petter Reinholdtsen wrote: > Are you still able to reproduce this? I'm trying to write a test case > to trigger this bug, but am unable to do so. This is the test code I > use, and it always report SigIgn: 0000000000000000 for both test > scripts. What am I doing wrong? Note that you need startpar version > 0.59 just uploaded to unstable to have support for the -e and -d options > to use startpar without running scripts in /etc/init.d/. :)
Thanks for keeping track of this one! Unfortunately, the issue is still present -- on an up-to-date Debian wheezy. I still have no clue who to trigger this behavior other than a reboot of those machines. I can still reliably fix it by a restart of the condor daemons once the machines are fully up. If there is anything I can try on those machines that would help you determine the problem please let me know. Thanks, Michael _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
