One of our users had asked about running WildFly and while putting together the package for it I noticed a call to copy_file_range was failing. In many cases these types of functions are opportunistic - that is they fall back on other less performant ways of doing the same thing.
While looking at a sample grpc program the other day a user had mentioned that certain socket options were not being honored in nanos. This is not surprising and there are quite a few things like this nanos might not support today - you'd be surprised how much code works regardless.
Nanos is not linux but sometimes we stub certain syscalls so that applications written under the assumption they run on linux still work under Nanos. sched_setscheduler, sched_get_priority_max, sched_get_priority_min are all syscalls we recently stubbed.
Security does not have to be the nightmare it is. You've got better things to do than dealing with VM sprawl. Show everyone how you were responsible for halving the infrastructure budget. Be the winner!
Schedule a Demo
