On 2021-02-25, Catalin Patulea wrote:
> I believe the right way this works it that:
> - ssh client closes session
> - dropbear closes the read end of command's stdout pipe
> - next time command writes to pipe, it receives SIGPIPE and dies
> Thus I don't think dropbear needs to explicitly kill
I have a small ash script that prints memory statistics once a second:
#!/bin/sh
while true
do
date
cat /proc/[0-9]*/stat |
awk '$23 > 0 {printf "%5d %20s %8d %5d\n", $1, $2, $23, $24}' |
sort -n
sleep 60
done
When I run that
alone can be
a huge amount of work.
--
Grant Edwards grant.b.edwardsYow! Used staples are good
at with SOY SAUCE!
gmail.com
).
debug1: Final hpn_buffer_size = 131072
debug1: HPN Disabled: 0, HPN Buffer Size: 131072
debug1: channel 0: new [client-session]
debug1: Enabled Dynamic Window Scaling
--
Grant Edwards grant.b.edwardsYow! This is a NO-FRILLS
, and for interactive use, that's true. The embedded system is
set up with a blank password mainly during development and testing
because it's a handy way to do automate testing using shell scripts
running on the development host. The password prompt breaks that.
--
Grant Edwards