seems like there may be a timing issue with the -X stuff command,
i had a script doing
screen -S foo -dm
screen -S foo -X stuff "/path/to/script.sh^M"
and when the system is very busy, sometimes, the 2nd command seems to
be completely ignored, there's no indication that anything was
written/exec
good, it was non-trivial for me to update to the latest screen version
(probably should have put in more effort),
but now i don't have to, thank you.
seems -x stuff stop working around 756 bytes (not exactly 756 but very
close),
and while it's fine and expected that screen has limits, it does not
produce any error! nothing printed to stderr, and it returns 0 (success
error code)
for example this works:
screen -S emergency_diskspace -dmsleep 1 #
