Yes, those are mainly Wordpress sites with MySQL. No sides effects so far. Are there plans to prevent that “Segmentation fault” and instead display an error message? If aio-nr is pretty standard in Linux (which it seems to be), then it would be easy just to check those values. Anyway, thanks again for all your help.
Yeah, I’d expect @freeekanayaka to at least correct the code path to handle errors properly rather than crash in that way ![]()
Yes, I’m fixing this as part of broader improvements around error handling and propagation. This particular error path is going to be fixed in the next C raft release.