Logs from kernel clutch in stdout with application logs.
I tried to add some logs on debugging #36 to sys-io/src/runtime/io_stats.rs:
crate::moto_log!(
"dangling wakers, will be processed in next loop... maybe: {:?}",
wakers
);
Thes lead to output like this on running ss command:
TCP: pid: 7 dev: 0 id: 17 local_addr: Some([:3:081:7]88: 20: 2US2ER 2 )s yrse-mioo t0xe2:_0xa5 d- 'd':r E:RRO R sNys-ioo/nsrc/ema ins.rts:a51t: epa:ni ckLedi ast tsyes-ino/sirc/rnungti me(/iLo_istsatts.erns):
:T1C7P::
_apsisedrt:io n 7` ldeeft v=:= 0r iigdh:t `19 f aliolceadl
aldedfrt:: S1
o rmigeht(: [0
:1]:2222) remote_addr: None state: Listening (Listen)
The kernel logs should either lock stdout or be written to a separated place mimic-ing dmesg.
Logs from kernel clutch in stdout with application logs.
I tried to add some logs on debugging #36 to
sys-io/src/runtime/io_stats.rs:Thes lead to output like this on running
sscommand:The kernel logs should either lock stdout or be written to a separated place mimic-ing dmesg.