Date: Sat, 23 Aug 2025 14:13:11 +0300 From: Anthony Pankov <anthony.pankov@yahoo.com> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: Vadim Goncharov <vadimnuclight@gmail.com>, David Chisnall <theraven@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com>, hackers@freebsd.org Subject: Re: My experiences with Rust Message-ID: <1614139543.20250823141311@yahoo.com> In-Reply-To: <20250823073225.ecf498cc3e7a6dcb68ccc3c8@dec.sakura.ne.jp> References: <aKiWZ1I3pqZSOsfk@kib.kiev.ua> <202508221712.57MHCPDl008201@critter.freebsd.dk> <E04D6E14-8EA1-446B-8C9C-762C9956F6D5@FreeBSD.org> <20250822214848.25569826@nuclight.lan> <202508221937.57MJbBtK008806@critter.freebsd.dk> <20250823002942.305119b2@nuclight.lan> <202508222133.57MLXtAA009189@critter.freebsd.dk> <20250823073225.ecf498cc3e7a6dcb68ccc3c8@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 августа 2025 г., 1:32:25 you wrote: .. > For output-only data from kernel TO BE LOGGED, text-only format would be > strictly wanted to read/process using oldies-but-goodies tools like > less, grep, awk, sed and any other thing to handle texts. I have a conceptual question. How to ensure reliability of recognizing events coded in log string? There is no information of all mutations which log string can take. 'grep "\d+ dropped"' will do the job well for "200 dropped" till log string has a form "dropped 100" or "150\s\sdropped". In latter cases event will be missed. I feel that there is, in principle, not enough information do solve the problem. But I don't think that structured data is the only cure. -- Best regards, Anthony Pankov mailto:anthony.pankov@yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1614139543.20250823141311>