I set the kill timeout to an arbitrarily high value just to see whether or not it'd pass and it appears to have gone through, unexpectedly... should this value be capped (because it's going to overflow with negative numbers potentially, depending on the bit-width of the number and the range chosen)? Thanks, -Garrett
Output: [nova-cavium5:/etc/init/jobs.d]$ cat kill_negative1 kill timeout 10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 [nova-cavium5:/etc/init/jobs.d]$ initctl start kill_negative1 [nova-cavium5:/etc/init/jobs.d]$ initctl status kill_negative1 [nova-cavium5:/etc/init/jobs.d]$ initctl status messagebus running rc4 not running control_2dalt_2ddelete not running rc5 not running rc6 not running job2 not running rc0 not running rc1 not running rcS not running job1 not running rc_2ddefault not running rc2 not running qauthJob not running rc3 not running sulogin not running kill_5fnegative1 running agetty running rcS_2dsulogin not running -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
