212 reputation
19
bio website
location
age
visits member for 2 years, 5 months
seen Sep 29 at 11:27

Nov
14
awarded  Popular Question
Nov
11
awarded  Popular Question
Sep
26
comment Control-p freezes SSH session
What kind of equipment - I connect to normal ARM development board, I don't know hardware details.
Sep
26
comment Control-p freezes SSH session
When SSH freezes touch /tmp/foo does not have any effect. Yes, I can use SSH escape sequences - I can leave session with . and list available commands with ?. I will do strace and post back the results.
Sep
24
comment Control-p freezes SSH session
I ran sshd -ddd on the server and connected to it on another subshell. After typing something debug log showed lines similar to debug3: Wrote 32 bytes for a total of 3103. When I pressed C-p both session when sshd was running and the one in which I pressed C-p froze. After that debug only showed debug1: server_input_global_request: rtype keepalive@openssh.com want_reply 1 interlaced with debug3: Wrote 32 bytes for a total of 3167 with different numbers after total of. I checked with stty -a that ^S is bound to stop.
Sep
24
revised Control-p freezes SSH session
deleted 1 character in body
Sep
24
comment Control-p freezes SSH session
it freezes inside cat and read also. I mean that it freezes.
Sep
24
awarded  Yearling
Sep
24
comment Control-p freezes SSH session
There is only one keybinding for C-p: "\C-p": previous-history. Command you suggested also prints "\C-x\C-x": exchange-point-and-mark
Sep
24
awarded  Custodian
Sep
24
reviewed Approve Control-p freezes SSH session
Sep
24
asked Control-p freezes SSH session
Jul
2
awarded  Curious
Oct
9
comment What's the idea behind rm not removing non-writable file by default?
I don't think I got your answer correctly. I wonder why rm issues such warning in a first place, why are read only files treated differently from writable files. I know when this warning is shown, I wonder why.
Oct
9
asked What's the idea behind rm not removing non-writable file by default?
Aug
26
accepted GNU screen - kill outer nested session
Aug
25
awarded  Commentator
Aug
25
comment GNU screen - kill outer nested session
No, redisplay doesn't change anything. I don't think screen is in a broken state, there are just 2 caption lines simultaneously one above the another.
Aug
25
asked GNU screen - kill outer nested session
Mar
27
accepted ps | grep shows bad output in subshell with jobs running in the background