On 14.10.2015 00:13, Richard W.M. Jones wrote:
On Tue, Oct 13, 2015 at 03:00:27PM -0600, Chris Murphy wrote:
Maybe strace will show where it gets hung up?
Tried it of course - strace doesn't work across the setuid boundary.
Maybe I can attach a trace tool (which?) to sshd (how?) and find out
where it is spending its time. This stuff should be easier ...
Sysdig [1] logs all (or some if filter is specified) syscalls via kernel
module (in binary format like tshark):
sysdig -w /tmp/all.scap
sysdig -r /tmp/all.scap
Kind regards,
Alek
[1] http://www.sysdig.org/install/
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
