The logic for no_set_pgrp in the start command was reversed, causing it to not be used in the exact situation where it'd be most useful.
Avoid close(STDIN). This wasn't causing any obvious problems, but it did mean that some subprocesses could get created with STDIN pointing to the yath executable or to other unexpected files.
The logic for
no_set_pgrpin thestartcommand was reversed, causing it to not be used in the exact situation where it'd be most useful.Avoid
close(STDIN). This wasn't causing any obvious problems, but it did mean that some subprocesses could get created withSTDINpointing to theyathexecutable or to other unexpected files.